[
http://jira.codehaus.org/browse/MRELEASE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133893#action_133893
]
Michael Sell commented on MRELEASE-163:
---------------------------------------
I run into this problem on my project as well, mine involving bringing in an
ant task dependency into the ant-run plugin.
> Dependencies in build.plugins section of pom do not have thier versions
> updated.
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-163
> URL: http://jira.codehaus.org/browse/MRELEASE-163
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Linux/Maven v2.0.4
> Reporter: Baron Reznik
> Attachments: MRELEASE-163-evaluation path.txt
>
>
> Inside my parent pom of a multimodule project, I have something that looks
> like:
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <dependencies>
> <dependency>
> <groupId>mygroupId</groupId>
> <artifactId>build-resources</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> ...
> The snapshot dependencies inside the <plugins> section are not resolved and
> updated on release as other dependencies elsewhere in the pom are. In my
> specific case, I am using the maven-checkstyle-plugin with a dependency that
> includes a custom checkstyle checker xml file inside an artifact. So, I would
> expect that on release, the snapshot dependency would be resolved and updated
> like all others. If more information is needed to replicate, please let me
> know.
--
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
