maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MNG-6351) Version range resolution for build plugins
Date Tue, 30 Jan 2018 15:59:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise updated MNG-6351:
-------------------------------------
    Issue Type: New Feature  (was: Bug)

> Version range resolution for build plugins
> ------------------------------------------
>
>                 Key: MNG-6351
>                 URL: https://issues.apache.org/jira/browse/MNG-6351
>             Project: Maven
>          Issue Type: New Feature
>          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)

Mime
View raw message