[
https://issues.apache.org/jira/browse/MCLEAN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958671#comment-17958671
]
Olivier Lamy commented on MCLEAN-20:
------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-clean-plugin#205|https://github.com/apache/maven-clean-plugin/issues/205].
> pom packaged (aggregtor) project files shouldn't activate "clean" to delete
> /target
> -----------------------------------------------------------------------------------
>
> Key: MCLEAN-20
> URL: https://issues.apache.org/jira/browse/MCLEAN-20
> Project: Maven Clean Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: David Boden
> Assignee: Benjamin Bentmann
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
