maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MCLEAN-20) pom packaged (aggregtor) project files shouldn't activate "clean" to delete /target
Date Sat, 06 Sep 2008 19:15:48 GMT


Benjamin Bentmann closed MCLEAN-20.

      Assignee: Benjamin Bentmann
    Resolution: Won't Fix

As said, excluding {{clean}} from the lifecycle is in general not appropriate for projects
with packaging "pom". You can however use the plugin parameter {{[skip|]}}
introduced in version 2.2 to selectively disabled cleaning for certain projects.

> pom packaged (aggregtor) project files shouldn't activate "clean" to delete /target
> -----------------------------------------------------------------------------------
>                 Key: MCLEAN-20
>                 URL:
>             Project: Maven 2.x Clean Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1
>            Reporter: David Boden
>            Assignee: Benjamin Bentmann
> 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
> 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:
For more information on JIRA, see:


View raw message