The following comment has been added to this issue:
Author: Cameron Fieber
Created: Wed, 5 May 2004 3:09 PM
Body:
the structure is as you described in the first case, however the top level project.xml
doesn't define any dependencies, it is just used to define the build structure,
resources, repository, developers, and groupId.
here's what happens:
before:
root
|-project.xml - just global values, developers, etc but no dependencies
|-componentA
| |-api
| | |-project.xml (extends root project.xml)
| |-impl
| | |-project.xml (extends root project.xml, depends on
componentA-api)
after (CVS update, someone added componentB, modified componentA-impl to use
componentB):
root
|-project.xml - just global values, developers, etc but no
| dependencies
|-componentA
| |-api
| | |-project.xml (extends root project.xml)
| |-impl
| | |-project.xml (extends root project.xml, depends on
| componentA-api, componentB-api)
|-componentB
| |-api
| | |-project.xml (extends root project.xml)
| |-impl
| | |-project.xml (extends root project.xml, depends on
componentB-api
What now happens, is that componentA has been built (has target directories), but you
can't do a multiproject:clean because componentB-api hasn't been built yet and the
multiproject:clean will detect the missing dependency for componentA-impl and fail.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=comments#action_19391
---------------------------------------------------------------------
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
Versions:
1.0-rc2
Assignee:
Reporter: Cameron Fieber
Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 3:09 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
