[jbosstools-issues] [JBoss JIRA] (JBIDE-11297) AS7 ability to add deployment folders on separate file systems

[ https://issues.jboss.org/browse/JBIDE-11297?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-11297. --------------------------------- Resolution: Done This is working as intended. The reason in your case the scanner is replaced is because the server should not be loading deployments from a previous workspace. The code works as follows: 1) determine what folders SHOULD be added. Determine this from the settings stored in the server editor. 2) Get the list of current deployment scanners from the app server 3) Remove any scanners that are in the list of step 2) but NOT in the list from step 1) who's names start with jbosstoolsscanner 4) Add any scanners which are in the list from step 1) which are NOT in the list from step 2) So... to get arbitrary folders added, you may perform the following: 1) create a new server 2) mark it as metadata 3) create a dynamic web project 4) in the server editor page 2, mark the new dynamic web project to deploy to /home/yourname/tmp/folder 5) deploy the project 6) start the server You will note here that the server will remove any scanners added from a previous workspace, then add the metadata folder, and then add the folder from step 4) In this way you can have each module deploy to a different folder, and a scanner for each folder will be added. The idea here is that a server should not be "infected" by another workspace using the same server. If workspace1 needs /home/rob/folder1 added to the deployment scanner list, there is no guarantee workspace2 needs that at all. Workspace2 most likely does not want /home/rob/folder1 added to the scanner list. In fact, the user would be very confused. (Why is my workspace1web.war deployed?! I'm in a different workspace!!) So we remove that scanner, and add only those which are relevant for the current server adapter object. This is working as intended -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira