On Sun, 12 Jun 2016 15:10:35 +0200, Christian Schulte <[email protected]>
wrote:
Am 06/12/16 um 15:01 schrieb Robert Scholte:
Based on the description "Make 'optional' flag of a dependency
manageable"
I would say -1 for this change.
Why?
Let me quote myself:
"I've been talking about this change with a couple of fellow committers at
FOSDEM and it convinced me that you never ever want to manage optional.
They have too much effect on the dependencies using it. For dependencies
which are expected to be non-optional (default) it suddenly will be.
Instead the ModelValidator should inform the users that setting the
optional-flag on a managed dependency has no effect."
Or is this the answer to global excludes?
It can be used to exclude a dependency globally by flagging it optional
in dependency management.
Maybe the description is misleading, because IIRC this is more about
transitive dependencies which were marked as optional. Those
dependencies
should not end up in the resolution.
No. It's about allowing to manage the optional flag the same way the
scope and version can be managed. What's wrong with that? It's a missing
feature.
Give Christian Schulte the chance to clarify this again, based on 2 or 3
poms. Hopefully that explains it a bit more. Issue has reached TLDR
status.
What is there I need to clarify?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
