[
https://jira.codehaus.org/browse/MRELEASE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321889#comment-321889
]
Lukasz Dywicki commented on MRELEASE-829:
-----------------------------------------
Workaround is to use exact version (1.0-SNAPSHOT) instead project.version
expression. Guilty is
[AbstractRewritePomsPhase.java#L534|https://github.com/apache/maven-release/blob/trunk/maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/AbstractRewritePomsPhase.java#L534]?
> ${project.version} is not replaced during release
> -------------------------------------------------
>
> Key: MRELEASE-829
> URL: https://jira.codehaus.org/browse/MRELEASE-829
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Maven 3.0.5
> Reporter: Lukasz Dywicki
>
> I have small project with organization parent and checkstyle resources
> packaged as JAR and built as parent sub-module.
> The checkstyle module is added as dependency to maven-checkstyle-plugin
> defined in parent:
> {{code:java}}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <configuration>
> <configLocation>code-house/checkstyle.xml</configLocation>
> <failsOnError>false</failsOnError>
> <failOnViolation>false</failOnViolation>
> </configuration>
> <dependencies>
> <dependency>
> <groupId>org.code-house</groupId>
> <artifactId>checkstyle</artifactId>
> <version>${project.version}</version>
> <optional>true</optional>
> </dependency>
> </dependencies>
> </plugin>
> {{code}}
> After release ${project.version} is not being replaced and released pom still
> contains ${project.version}. This causes usage of version from 3rd party
> child modules which should inherit settings from parent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
