[
https://issues.apache.org/jira/browse/MNG-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082452#comment-17082452
]
Elliotte Rusty Harold commented on MNG-6351:
--------------------------------------------
Version ranges are a real problem. I'd be more inclined to remove them from
dependencies than add them to plugins. But, yes, we could update the docs here.
> Version range resolution for build plugins
> ------------------------------------------
>
> Key: MNG-6351
> URL: https://issues.apache.org/jira/browse/MNG-6351
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Affects Versions: 3.5.2
> Environment: Windows 10
> Reporter: Max S.
> Priority: Minor
> Labels: documentation, features, maven, patch
>
> Hi,
> Maven's version range resolution does not work for build plugins, but for
> dependencies. Why? Our build process is depending on these plugins. Now we
> want to include Minor-Version-Bugfixes into our on these dependent
> applications. But somehow the previously so easy used version ranges for
> dependencies do not work for plugins. Why? Why you repeat yourself by not
> using the same code-basis for the same problem? There is also no way to
> resolve a version from a given version range string for a given artifact in
> the whole Maven API. Why? If it's so, why is that with the
> plugin-not-able-to-resolve-version-ranges not CLEARLY stated in the
> documentation? This very bad..
> What to do now?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
