The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Wed, 5 May 2004 2:49 PM
Body:
I think the problem is :
This problem is due to a bad directory structure.
You merged the build process and the project definition in the same structure.
root
|--project.xml (run multiproject from here)
|--subproject1
| |--project.xml (extend on project.xml in parent directory)
|--subproject2
| |--project.xml (extend on project.xml in parent directory)
Is it correct or similar?
The best way is :
root
|--project.xml (run multiproject from here, you don't need deps))
|--master
| |--project.xml (extend on project.xml in master directory)
|--subproject1
| |--project.xml (extend on project.xml in master directory)
|--subproject2
| |--project.xml (extend on project.xml in parent directory)
Emmanuel
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=comments#action_19389
---------------------------------------------------------------------
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 2:49 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]
