[
http://jira.codehaus.org/browse/MINSTALL-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173561#action_173561
]
Benjamin Bentmann commented on MINSTALL-63:
-------------------------------------------
The metaversion LATEST is meant for plugins only, not for regular dependencies.
For normal dependencies, you should be able to reach the same effect via
[version
ranges|http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges].
As for {{updateReleaseInfo}}, I believe the general idea is that if one doesn't
want to mark a version as release, then don't enable {{updateReleaseInfo}}.
Usually, {{updateReleaseInfo}} is only set inside a dedicated release profile
that users activate on demand during the release process.
Having said this, I feel this issue (and the related one) should be closed as
"Won't fix".
> 'LATEST' flag not getting updated
> ---------------------------------
>
> Key: MINSTALL-63
> URL: http://jira.codehaus.org/browse/MINSTALL-63
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install
> Affects Versions: 2.3
> Reporter: Sudhakar Kanagarajan
>
> Install plugin never updates the 'LATEST' flag in the artifact metadata. So
> the 'LATEST' version never gets resolved.
> Also if the 'updateReleaseInfo' is enabled, the release version in the
> artifact metadata gets updated even for a snapshot build.
--
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
