-0.9 for the commandline option, there should be only one truth.
Dependency management is way too important, you should not have an option
to choose. Better to agree that we are indeed fixing a bug or that we
should maintain the current behavior. And that'll take time. I will have a
look at all the related issues which could be controlled by this flag and
find a way to get feedback from more people.
I have a different proposal: suppose we could "autocorrect" the pom.xml
during distribution. I'm especially looking into MNG-5971. What happens if
the include-scope is used, but is being replaced with all the actual
included dependencies? Most important: do we get the expected behavior.
The advantage of this is that you can use a new scope in your pom.xml, but
in the repositories you will only see well-known scopes.
We should also have a look at the flatten-maven-plugin. Some parts are
quite interesting
This would be the first time where the projects pom wouldn't have to be
the same as the installed or deployed pom. I would like to work on that,
but for 3.5.x
Robert
On Wed, 21 Dec 2016 17:53:04 +0100, Christian Schulte <c...@schulte.it>
wrote:
Am 12/21/16 um 13:46 schrieb Christian Schulte:
ago. The next commits from me would be for the Maven site and for the
release notes. Except that command line option. Ok. It really depends on
That command line option got added with this commit:
<https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=7e70c59e43f112c12282de49d937e870c9545fc9>
It is lacking ITs to test the command line option really makes
everything behave as before. Will add some in the next days.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
