This one is just a little usability enhancement Description of problem: When defining includes/excludes in new drift there is no need to require path property not to be empty. For case, when I have base directory set to lets say /opt/drifts and I want to only specify a few include masks I am forced to put '.' into Path field. Version-Release number of selected component (if applicable): JON 3.0.0.CR2 How reproducible: always Steps to Reproduce: 1. Create new drift from File-System Template 2. Define some base dir 3. Specify you want to include only *.txt files within base dir Actual results: you are forced to insert '.' symbol to 'Path' property Expected results: It would be more simple if 'Path' property could be empty and would mean, include given mask within base directory Additional info:
(8:29:08 PM) ccrouch: jsanda: this seems a reasonable request: https://bugzilla.redhat.com/show_bug.cgi?id=755673, but for jon3 this should be a note in the docs right? (8:29:34 PM) jsanda: looking... (8:30:44 PM) jsanda: definitely a reasonable request (8:31:01 PM) jsanda: just trying to remember if there was a good reason we required the field to be non-empty (8:31:24 PM) jsanda: whatever the reason, must not have been good enough because i can't think of it :-)
master commit 84c83f8760f6f37f7b7eed1b5e27346691901c11 It's now optional. It will be set to "." by default in the GUI. But even if omitted will again get set to "." at the lower levels.
verified RHQ 3, master. observed the default set to '.' ... and additionally tested with that '.' omitted.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE