[jira] Closed: (MAVEN-1251) Properties aren't being overriden in maven.xml

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Fri, 7 May 2004 6:57 PM

it is a side effect of the way plugins are loaded that the first one sets at all. This will be corrected in future versions of Maven, but not 1.0.

Instead of using j:set, you need to use the maven:set tag to set plugin properties from Jelly. I have added this to the FAQ in CVS
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1251

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1251
    Summary: Properties aren't being overriden in maven.xml
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:
             1.0-rc3
   Versions:
             1.0-rc3

   Assignee: 
   Reporter: Chad Brandon

    Created: Fri, 30 Apr 2004 10:14 PM
    Updated: Fri, 7 May 2004 6:57 PM
Environment: Windows XP, JDK 1.4.2

Description:
I've just built MAVEN-1_0-BRANCH today (04-30-2004) and I've noticed some strange behavior:  I have two goals which use multiproject:install. I set the 'maven.multiproject.includes' property to the POMS that need to be built during each goal.  The goal directly below is called first and then the goal below that is called next (as part of the same build).  

Now 1.0-rc3 from a couple weeks ago doesn't have this problem (and neither do any earlier releases like 1.0-rc2) but now it looks like when the 'install-samples' is called (the second goal below), the first maven.multiproject.includes value is used because the same components are built again instead of the new ones. 

So basically what happens is: all modules defined with ${component.install.includes} are built twice and the modules defined by ${sample.install.includes} are never called.  

<goal name="install-components">
  <j:set var="maven.multiproject.includes" 		 value="${component.install.includes}"/>
  <attainGoal name="multiproject:install"/>	
</goal> 

the second goal:

<goal name="install-samples">
  <j:set var="maven.multiproject.includes" 
         value="${sample.install.includes}"/>
  <attainGoal name="multiproject:install"/>	
</goal>  


---------------------------------------------------------------------
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org