[ https://jira.jboss.org/browse/JBIDE-6312?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-6312: ------------------------------------ I am absolutely not able to replicate this. Changing to metadata, default, or custom, seems to work 100% for me. This is of course depending on that you remove a module from the server (and possibly publish) before changing its deploy location. I have just tested this for 15 minutes and have not replicated any unexpected behaviour. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6312?page=com.atlassian.jira.plugin.s... ] Jiri Peterka reopened JBIDE-6312: --------------------------------- Rob, strange, I don't have problem with reproducing so I hope I understand well this functionality. So Server -> Deployment tab > Local Deployment -> Default Setting: I assume this: This default setting says where web application should be deployed until I set different custom location in modules table, right? Of course after previous undeployment and stopping the server. I'll try to give you the most simple example of non-working situation (JBDS 3.0.1 GA) with clear workspace with bundled jboss-eap server: 1. Create custom folders for example /home/{username}/tmp/server/deploy and /home/{username}/tmp/server/tmp 2. Set JBoss deploy folder as default deploy folder, save setting 3. Create jsf 1.2 project kickstart 4. Start the server, deploy jsf project 5. Undeploy, stop the server change to custom deploy folder (you've created), save 6. Start the server, deploy jsf project ERROR: Project is again deployed in JBoss deploy folder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6312?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-6312: ------------------------------------ I've replicated it now... good catch. Now I get to trace through and find out what the hell is changing that on new projects =] I've even replicated it on Dynamic webs so I'm fairly sure it's not jbt projects causing it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6312?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-6312: ------------------------------------ GOT it... some parts of my editor code are not gaining access to the new working copy after a modification to whats published is executed. Damn... that took way too long to track down. ugh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6312?page=com.atlassian.jira.plugin.s... ] Jiri Peterka commented on JBIDE-6312: ------------------------------------- Nice :). So fix version is 3.2.0.M1, right? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira