Hi,
a very short conclusion of[1] it is:
"The intention of prerequisites was to prevent maven plugins running
with the wrong Maven versions"...
If you need to require a particular Maven version (for whatever reason)
you should do that via maven-enforcer-plugin....
Kind regards
Karl Heinz Marbaise
[1]: http://blog.soebes.de/blog/2015/04/04/maven-prerequisites/
On 7/9/16 9:57 PM, Hilco Wijbenga wrote:
On 9 July 2016 at 03:09, Robert Scholte <rfscho...@apache.org> wrote:
prerequisites are never inherited, see
https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/merge/MavenModelMerger.java#L190
Does anyone know why that is? At first glance, that seems rather
unhelpful. You have to repeat the prerequisites in each POM instead of
putting it in the parent once. Why would you ever want to build child
A with different prerequisites than child B? (And if you did come up
with a use case, you could simply override the prerequisites in that
particular child's POM.)
Perhaps there are non-obvious technical difficulties?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
