[jbosstools-issues] [JBoss JIRA] (JBIDE-11792) Incomplete deploy after undeploying and deleting a current deploy

[Lukas Kalinski (JIRA)]

Lukas Kalinski created JBIDE-11792:
--------------------------------------

             Summary: Incomplete deploy after undeploying and deleting a current deploy
                 Key: JBIDE-11792
                 URL: https://issues.jboss.org/browse/JBIDE-11792
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: JBossAS/Servers, maven
    Affects Versions: 3.2.2.Final
         Environment: Eclipse 3.7.2 @ Mac OSX 10.7.3 (Lion), MacBook Air
            Reporter: Lukas Kalinski
            Assignee: Rob Stryker


As I don't have time to reformulate myself, I just post what I've written on the forum earlier:

I recently installed Eclipse 3.7.2 on Mac OSX 10.7.3 (Lion), together with the latest JBoss Tools package. As I am new to JBoss Tools (and Apache Maven that it's using in my projects) I decided to get familiar with it before going on with something serious. So I created a new JBoss Central/Spring MVC Project. After that I added a server instance (JBoss AS 7.1.1) inside Eclipse, and deployed this unmodified project template using the Project/Run As/Run on server way. This works perfectly! However, if I for some reason decide that I would like to undeploy the project, and then deploy it again (i.e. undeploy using JBoss Management, then delete the exploded war-dirs, restart the server, and finally deploy as described above), I end up with everything being deployed, EXCEPT for everything that is in the webapp directory (the one that's created by default in this project template). As a consequence, the web application won't run anymore.


Now this is what I've tried without any success:

- Restart Eclipse;

- Delete every possible file in the JBoss AS directory, that could have something cached inside it;

- Committed the whole project tree into GIT, in order to check whether Eclipse changes some config setting (it doesn't);

- Various combinations of the above, together with a lot of other not-remembered steps ...

I could add to this that what "solves" the problem is to refactor the project name to a new one; eg, if your project is called test, then refactor it to test2 and the problem is solved. When going back to the old name ("test" in the mentioned example), the problem will still be gone. This is not a nice solution however (especially if you have your project in git/svn etc) ... and the fact that it works makes the whole problem even more weird.

--
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