[jira] [Commented] (MNG-6351) Version range resolution for build plugins

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345280#comment-16345280 ] 

Karl Heinz Marbaise commented on MNG-6351:
------------------------------------------

Instead of complaining I would suggest to make suggestions to improve it. For example creating suggestions how the documentation should be changed from your point of view...maybe you can create a patch for it...furthermore for the version range solution of plugins or dependencies in consequence it means that you will leave reproducibility behind you...Plugins are not changed very often compared to dependencies (I would never you version ranges for dependencies; This is a different story)..
But if you like you can create a patch against maven core to support version ranges for plugins?

So apart from the above if i correctly understand that you have a plugin using in a particular version in your project and you like to upgrade it...Ok so what is the real problem here? To change the pom file accordingly to use a new version ? 

> Version range resolution for build plugins
> ------------------------------------------
>
>                 Key: MNG-6351
>                 URL: https://issues.apache.org/jira/browse/MNG-6351
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.5.2
>         Environment: Windows 10
>            Reporter: Max S.
>            Priority: Major
>              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
(v7.6.3#76005)