[
http://jira.codehaus.org/browse/MRELEASE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120277
]
Baron Reznik commented on MRELEASE-163:
---------------------------------------
you are correct that you could release the resource separately. however, i was
trying to save time in managing the pom dependency versions and didn't want to
have to manually update the version every time the resource was updated. on
large software projects, the time management required for the build/release
process (whether it's ant, maven, otherwise) can take up a large amount of
time, so cutting down on that time was beneficial, and I think this made things
simpler. keeping it as snapshot and having the release plugin update the
versions means there's no need to keep the resource in a project under a
separate SCM trunk so that it could be easily built/released independently.
there's probably a couple other reasons I could list, but the basic idea was to
keep things as simple as possible to save time.
i'm not sure the remote-resource-plugin would help in this case, but regardless
of the specific use case - does it seem reasonable that the dependencies under
a plugin should have their versions updated/promoted during a release the same
as dependencies listed elsewhere in the pom?
> 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
