Am 21.08.2016 um 17:19 schrieb Karl Heinz Marbaise:
We need to find a better way for those things...May be this is exactly a
sitution to control the behaviour via a feature flag to change this. So
anybody can decide to use the new (correct) behaviour or keep the old
behaviour...(which could be defined as the default).
You cannot deploy such POMs as well. Using command line options to
control model building behaviour is not possible.
cmd> mvn --my-very-special-flag deploy
Someone consuming this pom also needs to add '--my-very-special-flag' to
get the same result. Not even possible to print a warning about lack of
that flag.
As a first step we could emit warnings about those wrong pom's and give
the user the hint that he could change that by using feature flag or
better to fix the wrong pom files...
That's what I did. The warnings are not due to the change to the import
scope. They would appear without any change to the import scope as well.
Introducing an new `include` scope might be solution which might be
discusses more in detail...
Increase the model version, introduce the include scope, or revert the
changes. Just someone tell me what to do, please.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
