[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1390) After removing maven dependency, JBDS does not `mvn clean` nor redeploy.

[Max Andersen (JIRA)]

    [ https://jira.jboss.org/browse/JBDS-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565522#comment-12565522 ] 

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.

> After removing maven dependency, JBDS does not `mvn clean` nor redeploy.
> ------------------------------------------------------------------------
>
>                 Key: JBDS-1390
>                 URL: https://jira.jboss.org/browse/JBDS-1390
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>    Affects Versions: 4.0.0.M2
>            Reporter: Ondrej Zizka
>             Fix For: 4.0.0.CR1
>
>
> 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/project/branches/practice03-jpa
> 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?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira