You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/05/06 01:09:37 UTC

[jira] Updated: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Wed, 5 May 2004 7:08 PM
    Comment:
It's a good point, but it won't be fixed in 1.0 unfortunately
    Changes:
             Fix Version changed to 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1270
    Summary: multiproject:clean fails due to dependencies in reactor set
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:
             1.1
   Versions:
             1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

    Created: Wed, 5 May 2004 2:18 PM
    Updated: Wed, 5 May 2004 7:08 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

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.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report 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