maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Buechler (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-3817) Property inheritance when filtering with multiple profiles is gone
Date Thu, 13 Nov 2008 13:00:13 GMT

     [ http://jira.codehaus.org/browse/MNG-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Buechler closed MNG-3817.
--------------------------------

    Resolution: Fixed

The findings:

mvn 2.0.9 uses per default 

maven-resources-plugin-2.2
maven-war-plugin-2.1-alpha-1

while

mvn 2.0.8 uses per default 

maven-resources-plugin-2.3
maven-war-plugin-2.1-alpha-2

this is pretty weird, since the newer version uses the older plugins.

To get the behaviour of mvn 2.0.8. into 2.0.9 one has to provide explicit versions for both
plugins in

a parent pom's pluginmangement section like 

...
<build>	
		<pluginManagement>
			<plugins>
				<plugin>
					<groupId>org.apache.maven.plugins</groupId>
					<artifactId>maven-resources-plugin</artifactId>
					<version>2.3</version>
				</plugin>
				<plugin>
                                       <groupId>org.apache.maven.plugins</groupId>
                                       <artifactId>maven-war-plugin</artifactId>
                                      <version>2.1-alpha-2</version>
                                </plugin>
			</plugins>
		</pluginManagement>
	...


or directly at the plugin definition.






> Property inheritance when filtering with multiple profiles is gone 
> -------------------------------------------------------------------
>
>                 Key: MNG-3817
>                 URL: http://jira.codehaus.org/browse/MNG-3817
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 2.0.9
>            Reporter: Martin Buechler
>            Priority: Blocker
>             Fix For: 2.0.9
>
>         Attachments: MNG-3817.zip
>
>
> pom.xml:
> <build>
>        <filters>                    
>              <filter>default.properties</filter>
>          </filters>
> </build>
> <profiles>	
> 	<profile>
>             <id>first</id>
>             <build>
>                 <filters>                    
>                     <filter>first.properties</filter>
>                 </filters>
>             </build>
>         </profile>
> 	 <profile>
>             <id>second</id>
>             <build>
>                 <filters>                    
>                     <filter>second.properties</filter>
>                 </filters>
>             </build>
> ...
> default.properties:
> prop=
> first.properties:
> prop=first_value
> second.properties:
> other_prop=${prop}
> since 2.0.9 the value of 
>     other_prop 
> is not replaced and is written as ${prop}, instead of inherit the value 'first_value',
when executing
>    mvn -Pfirst,second process-resources
> This breaks existing configurations badly and I do not see a workaround whithout losing
the ability to configure in more than one dimension, which makes mvn 2.0.9 quite unsuable
for project requirements in real life.
> 	

-- 
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

        

Mime
View raw message