jira-importer commented on issue #223:
URL: 
https://github.com/apache/maven-install-plugin/issues/223#issuecomment-2771852486

   **[Benjamin 
Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)**
 commented
   
   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".
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to