The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Aug 2003 10:36 AM
Changes:
timeoriginalestimate changed from 0
timeestimate changed from 0 minutes
Fix Version changed to 1.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-440&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-440
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-440
Summary: Reactor handles badly goals redefined in subproject
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
maven-reactor-plugin
Fix Fors:
1.1
Versions:
1.0-beta-10
Assignee:
Reporter: Florin Vancea
Created: Thu, 22 May 2003 2:10 AM
Updated: Mon, 4 Aug 2003 10:36 AM
Environment: W2k, JDK1.3.1, Maven from CVS HEAD (2003-May-21)
Description:
Context: several projects, aggregated under a master project. Each one performs well
by itself. Master is running goals over children subprojects using simple reactor
setup.
Problem: One of the subprojects redefines a "standard" goal in its maven.xml (I tested
with "clean" and with "cactus"). That particular project runs fine, the very following
one complains with "Unknown goal".
There is no way to run the reactor over the set without changing the logic that led to
overwriting that goal. Of course one could (sometimes) rewrite the logic, but I
believe that the reactor should run the subprojects in fully "encapsulated" contexts,
even if this creates an additional time/space cost.
Using a sequence of <maven:maven> calls instead of the reactor produces similar
results (+ one explicit UnknownGoalException ).
I believe also the problem is related to MAVEN-249 and MAVEN-231.
I experienced also some other odd behavior which is not exactly the one described
above, but all the above seem to have one common cause.
Yes, I think it's major (as reporters on above issues considered, too) because using
the reactor is one (the only?) neat way to maintain large sets of dependent projects.
I'm sorry, I have no suggestion, solution or workaround: I did not dig _that_ deep
into props/goals/jelly handling ;)
If a "proof" setup is required, I can produce one.
---------------------------------------------------------------------
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]
