[ https://jira.jboss.org/browse/JBDS-1390?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka updated JBDS-1390: ------------------------------- Fix Version/s: 4.0.0.CR1 Affects Version/s: 4.0.0.M2 Description: After removing maven dependency, JBDS does not `mvn clean` nor redeploy, so the dep stays in the deployed application when you do "Run As... -> Run at server". STR: 1) svn export -r12016 https://svn.devel.redhat.com/repos/jboss-qa/people/ozizka/VUTcourse/proje... 2) Import to JBDS with all the other stuff - m2eclipse etc. 3) Run at server. 4) In pom.xml, remove HSQL, and add <scope>provided</scope> to Hibernate. 5) Run at server. 6) Check the deployed app; it still has both jars inside. Shame :-) Is it upstream? was: After removing maven dependency, JBDS does not `mvn clean` nor redeploy, so the dep stays in the deployed application when you do "Run As... -> Run at server". STR: 1) svn export -r12016 https://svn.devel.redhat.com/repos/jboss-qa/people/ozizka/VUTcourse/proje... 2) Import to JBDS with all the other stuff - m2eclipse etc. 3) Run at server. 4) In pom.xml, remove HSQL, and add <scope>provided</scope> to Hibernate. 5) Run at server. 6) Check the deployed app; it still has both jars inside. Shame :-) -- 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/JBDS-1390?page=com.atlassian.jira.plugin.sy... ] Max Andersen commented on JBDS-1390: ------------------------------------ If you remove the dependencies and you want that reflected then you need to run the build - that is not something that should be done automatically IMO. And if it was - yes, it is upstream. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira