Am 06/12/16 um 15:40 schrieb Robert Scholte:
>>
>> 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. F
Hi Christian,
On 6/12/16 3:48 PM, Christian Schulte wrote:
That will all go into the release notes, of course. There is more to
come. Before we go any further. I've just pushed a MNG-6006 branch. Do this:
Which couldn't be done yet cause the sub tasks are not completed. As i
mentioned in the
Am 06/12/16 um 15:01 schrieb Robert Scholte:
>> Hi,
>>
>> based on the feedback of the tests for current Maven 3.4.0-SNAPSHOT
>> testing I have taken a deeper look into some of the changes.
>>
>> Based on the above issue we now have changed the behaviour of Maven
>> 3.4.0 compared to 3.3.9 (and
On Sun, 12 Jun 2016 15:10:35 +0200, Christian Schulte
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 co
Hi,
On 6/12/16 3:10 PM, Christian Schulte 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?
At the moment (I'm not sure about this) is that this change is changing
behaviour in
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?
> Or is this the answer to global excludes?
It can be used to exclude a dependency globally by flagging it optional
in dependency man
Based on the description "Make 'optional' flag of a dependency manageable"
I would say -1 for this change. Or is this the answer to global excludes?
Even then I'm -1 and prefer extra elements in the model 5.
Maybe the description is misleading, because IIRC this is more about
transitive dep
Hi,
based on the feedback of the tests for current Maven 3.4.0-SNAPSHOT
testing I have taken a deeper look into some of the changes.
Based on the above issue we now have changed the behaviour of Maven
3.4.0 compared to 3.3.9 (and before).
It looks like this change breaks some builds...
So
