Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Wed, 26 May 2004 8:57 AM
design flaw in the current core means that the plugin has to be loaded first, which
can only be done via the use of goals and tag libraries at this point (having
maven:set load up the plugin causes problems downstream - I tried).
You'll need to use a dependency handle (soon to be documented: see
test:dependency-handle), or a multiproject goal prereq.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1289
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1289
Summary: Plugin properties can't be set
Type: Bug
Status: Closed
Priority: Blocker
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0-rc3
Assignee:
Reporter: Chad Brandon
Created: Thu, 20 May 2004 3:23 PM
Updated: Wed, 26 May 2004 8:57 AM
Environment: Windows XP, JDK 1.4.2
Description:
I just downloaded the maven-1.0-rc3 release. One of the issues I had had with a
SNAPSHOT version of maven-1.0-rc3 was that with <j:set var="someProperty"
value="someValue"/>, it would only set the plugin property the first time, but after
that, the plugin property could not be set to a new value, See MAVEN-1251. Anyway,
there were new tags introduced to deal with plugin properties (the new maven set and
get tags):
<maven:set
plugin="maven-multiproject-plugin"
property="maven.multiproject.includes"
value="**/*.project>
My problem is the new maven set tags don't seem to be setting the properties in the
plugin itself. If I use the maven:set tag to set a property like you see above, and
echo that property directly below it the property seems to be set.
No if I edit the maven-multiproject-plugin plugin.jelly file and do an echo, that
property isn't set....the property is ignored and the multiproject:install is executed
with the default property. I also tried the old version of setting the property with
the same result:
<j:set var="multiprojectPluginContext"
value="${pom.getPluginContext('maven-multiproject-plugin')}"/>
<j:set var="includes" value="**/*.project.xml>
<j:set var="dummy"
value="${multiprojectPluginContext.setVariable('maven.multiproject.includes',
includes)}"/>
Is there anyway to get around this?
---------------------------------------------------------------------
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]
