[ 
http://jira.codehaus.org/browse/MRELEASE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185422#action_185422
 ] 

Mike Youngstrom commented on MRELEASE-466:
------------------------------------------

Oops my bad.  I guess it only resolves the scm elements.  Which is still a 
problem for my case but not as severe.  Here is an example pom.  I'm using 
Maven 2.2.

<project xmlns="http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
        <modelVersion>4.0.0</modelVersion>
        <groupId>test</groupId>
        <artifactId>test</artifactId>
        <version>1.0-SNAPSHOT</version>
        <packaging>pom</packaging>

        <properties>
                <jiraId>1234</jiraId>
                <moduleId>test</moduleId>
        </properties>

        <issueManagement>
                <system>JIRA</system>
                <url>http://jira&amp;component=${jiraId}</url>
    </issueManagement>
    
        <scm>
                <connection>scm:svn:https://someFakeSCM/${moduleId}</connection>
                
<developerConnection>scm:svn:https://someFakeSCM/${moduleId}/trunk/</developerConnection>
                <url>https://someFakeSCM/${moduleId}</url>
        </scm>
    
    <build>
        <pluginManagement>
                <plugins>
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-release-plugin</artifactId>
                                <version>2.0-beta-9</version>
                        </plugin>
                </plugins>
        </pluginManagement>
    </build>
</project>

> Release plugin should preserve pom properties and ${...} variables
> ------------------------------------------------------------------
>
>                 Key: MRELEASE-466
>                 URL: http://jira.codehaus.org/browse/MRELEASE-466
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.0-beta-9
>            Reporter: Mike Youngstrom
>
> When I run release:prepare on a parent pom with properties and ${...} 
> variables they get resolved in the release plugin created pom.  It would be 
> nice if these ${...} variables could remain unchanged.  This is usually a 
> problem in the case of parent poms that expose properties for their children 
> to use to override certain values.  The release plugin's removing of these 
> variables makes it so that child poms dependent upon these properties no 
> longer work.

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

        

Reply via email to