this needs to be tested: if I have a bundle deployed with managedRootDir=false, and I elect to purge that bundle, only the bundle files should be removed - all files that are external to the bundle should remain. For example, suppose I have an EAP instance installed (non-bundle install), and I have things deployed in the deploy/ directory: /opt/eap5/server/default/deploy/jmx-console.war for example. Now suppose I have a bundle with manageRootDir=false and I put it in deploy/ /opt/eap5/server/default/deploy/my-bundle.war where the bundle distribution has "my-bundle.war" as the top directory (in other words, the destination directory was "deploy/"). If I purge that bundle, the deploy/my-bundle.war should go away, but jmx-console.war (and all other things in deploy/) should remain intact and left alone. Question: does it? We need to test this scenario and make sure it works as we think it should. Otherwise, we need to fix it.
This should be tested on JON2.4.1 and JON3.0.0
(In reply to comment #1) > This should be tested on JON2.4.1 and JON3.0.0 This purge feature did not exist in JON 2.4.1 in the first place, so, there is nothing to test :)
I think this is supported... looking at code in org.rhq.plugins.ant.AntBundlePluginComponent it does look at the manageRootDir setting.