The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Aug 2003 10:34 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-249&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-249
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-249
Summary: custom tag define in reactored subproject available in main and other
subproject
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
maven-reactor-plugin
Fix Fors:
1.1
Versions:
1.0-beta-8
Assignee: Jason van Zyl
Reporter: Colin Sampaleanu
Created: Mon, 3 Feb 2003 3:53 PM
Updated: Mon, 4 Aug 2003 10:34 AM
Environment: CVS HEAD 2003-2-3, win2k
Description:
This touchstone test shows that if the reactor is used to run subprojects, there seems
to be some pollution of the parent jelly context, as well as contexts for subsequent
reactor builds. While variable defined in the subproject do not seem to persist (which
is good), custom tags defined in one one subproject persist back to the parent
project, or another subproject run via the reactor.
Note that these files were generate on Windows with CR/LF line endings. Any checkin on
a unix system should first strip extra CR from end, or files will check in with extra
CR on each line. I would prefer to upload a patch, but while it's easy to do a diff
on files that are modified from the repo, I do not know how to do a diff on new files
added, when I do not have write access to the repo.
---------------------------------------------------------------------
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]
