[ http://jira.codehaus.org/browse/MCLEAN-20?page=comments#action_77252 ] David Boden commented on MCLEAN-20: -----------------------------------
This chap is having the same issue: http://mail-archives.apache.org/mod_mbox/maven-users/200604.mbox/[EMAIL PROTECTED] > pom packaged (aggregtor) project files shouldn't activate "clean" to delete > /target > ----------------------------------------------------------------------------------- > > Key: MCLEAN-20 > URL: http://jira.codehaus.org/browse/MCLEAN-20 > Project: Maven 2.x Clean Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: David Boden > > If you have projects with the following layout: > cds_adapter/pom.xml > cds_adapter/pom-complete.xml - an aggregator > deriv_adapter/pom.xml > Then when you do: > mvn -f pom-complete.xml clean install > what you want is for deriv_adapter's jar to be built and installed followed > by cds_adapter's jar. > This happens. However, unfortunately the last thing to run is the "clean > install" task on the pom-complete.xml project. This deletes the > cds_adapter/target directory. The desired behaviour would be for the > aggregator pom not to result in the deletion of the /target directory. > Aggregator poms do not install anything into "target" and should not take > part in the "clean" workflow. > The workaround is to issue the commands separately: > mvn -f pom-complete.xml clean > mvn -f pom-complete.xml install -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
