You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/16 07:31:34 UTC
[jira] Updated: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set
[ http://jira.codehaus.org/browse/MAVEN-1270?page=all ]
Brett Porter updated MAVEN-1270:
--------------------------------
Fix Version: 1.1-beta-1
Description:
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.
was:
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.
> multiproject:clean fails due to dependencies in reactor set
> -----------------------------------------------------------
>
> Key: MAVEN-1270
> URL: http://jira.codehaus.org/browse/MAVEN-1270
> Project: maven
> Type: Improvement
> Versions: 1.0-rc2
> Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2
> Reporter: Cameron Fieber
> Priority: Minor
> Fix For: 1.1-beta-1
>
>
> 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 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org