[
https://jira.codehaus.org/browse/MAVEN-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MAVEN-1270.
---------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> multiproject:clean fails due to dependencies in reactor set
> -----------------------------------------------------------
>
> Key: MAVEN-1270
> URL: https://jira.codehaus.org/browse/MAVEN-1270
> Project: Maven 1
> Issue Type: Improvement
> Affects Versions: 1.0-rc2
> Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2
> Reporter: Cameron Fieber
> Priority: Minor
>
> I appologize if this is already entered, but I was unable to find it
> searching JIRA. This is the same as or similar to #MAVEN-443 which was
> marked as can't reproduce.
> If you have a multiproject build, you can't execute clean until all artifacts
> in that build that depend on other artifacts in the build have been produced.
> The ideal behaviour of multiproject:clean would be to either ignore
> dependencies not needed for the clean task itself, or consider a dependency
> satisfied if it is in the reactor set.
> The case where this feature would be a particular benefit is when you have an
> existing source tree, which has been built, and a new component is added. If
> you do an update and pulling down the new component it has yet to be
> compiled. You then can't do multiproject:clean on your existing tree because
> the new dependencies to the new component can't be resolved.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
