Hi Robert,
> 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
thank you (and other on this thread).
FYI, I filed a bug [1] with the versions-maven-plugin to reword their
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
On 9 July 2016 at 03:09, Robert Scholte 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
unhelpfu
Hi Andreas,
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
thanks,
Robert
On Wed, 06 Jul 2016 11:51:46 +0200, Andreas Sewe
wrote:
Hi,
I am confused by the foll
Hi,
I am confused by the following message of dependency:display-plugin-updates
> [INFO] Project inherits minimum Maven version as: 3.0
and this statement from the enforcer rule [1]:
> This rule enforces that the prerequisite is specified since it is not
> inherited from its parent.
Am I mi
