maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Max S. (JIRA)" <>
Subject [jira] [Commented] (MNG-6351) Version range resolution for build plugins
Date Tue, 30 Jan 2018 22:41:00 GMT


Max S. commented on MNG-6351:

Yeah I know. I should fix it by my self in my spare time ;) This is what they are telling
me also on my questions on the npm-stuff, too. I don't think companies do like it, when one
their employers waste some hours of work :) Only because documentation pages like this one:
is missing the information, that all of that is not applyable to plugins even id the style
of referencing is exactly the same. Who should know? ;) And I know, yeah open-source don't
comply, but also one like me have on person above me which I must explain then, that an idea
cannot be used on the second part as it seams.. 

_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).._

We only wanted automatic version resolving on the bugfix-level, not for major or minor updates..
Nobody wants the dependency-hell of Npm.. ;) So option is always great, so like it works for
maven-dependencies. :) Thanks

> Version range resolution for build plugins
> ------------------------------------------
>                 Key: MNG-6351
>                 URL:
>             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

View raw message