ctrueden commented on pull request #121: URL: https://github.com/apache/maven/pull/121#issuecomment-972108495
@dejan2609 @khmarbaise I use LATEST and RELEASE a lot for various purposes, such as CLI tooling that automatically synthesizes POMs to perform various tasks. I personally feel deprecating these metaversions was a mistake—I find them incredibly useful, with the understanding that I would never use them for production reproducible builds. But I do understand the rationale: we don't want to encourage anyone to use these in a way that harms the stability of dependency resolution, reproducibility-wise. So I'm OK with it, as long as there is a migration path forward for these sorts of use cases. But what is that path? I cannot find a way to replicate either of the metaversion behaviors using version ranges. There are problems with version ranges ([MNG-3092](https://issues.apache.org/jira/browse/MNG-3092), [MNG-6049](https://issues.apache.org/jira/browse/MNG-6049)) preventing them from being used as a replacement for LATEST or RELEASE. Furthermore, in my tests, specifying a version range like `[0,)` causes Maven to download POMs at a bunch of (maybe all?) versions of an artifact, whereas `LATEST` and `RELEASE` do not trigger en masse downloading.l Is there a non-deprecated syntax that has equivalent behavior? As things stand, I am concerned that support for these metaversions is going to disappear in a future version of Maven. If there is no way to achieve the metaversion behavior without them, please let me know, so that I can open an issue on the JIRA. Thanks! -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
