[jira] Commented: (MAVEN-1691) Variable scope problem

["Lukas Theussl (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MAVEN-1691?page=comments#action_65313 ] 

Lukas Theussl commented on MAVEN-1691:
--------------------------------------

It is indeed a bug in jelly and it has already been fixed in svn: http://svn.apache.org/viewcvs.cgi?rev=227285&view=rev

Unfortunately, with the current jelly 1.1-SNAPSHOT, I see a whole bunch of other test failures in our plugins, but at least your attached test case works!

> Variable scope problem
> ----------------------
>
>          Key: MAVEN-1691
>          URL: http://jira.codehaus.org/browse/MAVEN-1691
>      Project: Maven
>         Type: Bug

>   Components: jelly/ant integration
>     Versions: 1.1-beta-2
>     Reporter: Arnaud Heritier
>     Assignee: Arnaud Heritier
>     Priority: Blocker
>      Fix For: 1.1-beta-3
>  Attachments: plugin-test.zip
>
>
> There's a bug in m1.1 that doesn't exist in m1.0.X
> When you define a variable in a custom goal for a project, this last one is available for others projects.
> It cause a problem for example if you use several multiproject:goal.
> We have this problem in maven-plugins when we launch the goal plugins:test-all
> If a plugin use the multiproject with a new goal (<j:set:var="goal" ...), than the reactor use this goal for all plugins after it.
> I attached a test case for the multiproject plugin. It works with maven 1.0.2 but not with maven 1.1-beta2.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira