Christian you need to be proactive and sort this out...
FTR as release manager for Maven core 3.5.0 I have an easy answer to any
decisions asked of me: my answer is Out! For example, If there is a S1/S2
bug in coloured logging, then either it gets fixed promptly or it is out. I
will be brutal to
Am 03/10/17 um 23:33 schrieb Christian Schulte:
> Am 03/10/17 um 20:16 schrieb Robert Scholte:
>> On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte
>> wrote:
>>
>>> Am 03/10/17 um 10:42 schrieb Robert Scholte:
Having a closer look at this commit, I actually don't like
Am 03/10/17 um 20:16 schrieb Robert Scholte:
> On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte
> wrote:
>
>> Am 03/10/17 um 10:42 schrieb Robert Scholte:
>>> Having a closer look at this commit, I actually don't like the idea that
>>> ModelResolver now supports
On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte
wrote:
Am 03/10/17 um 10:42 schrieb Robert Scholte:
Having a closer look at this commit, I actually don't like the idea that
ModelResolver now supports versionRanges.
IMO the version should always be specific *before*
Am 03/10/17 um 10:42 schrieb Robert Scholte:
> Having a closer look at this commit, I actually don't like the idea that
> ModelResolver now supports versionRanges.
> IMO the version should always be specific *before* resolving the model.
> IIUC correctly this is required to supported
Having a closer look at this commit, I actually don't like the idea that
ModelResolver now supports versionRanges.
IMO the version should always be specific *before* resolving the model.
IIUC correctly this is required to supported version-ranges for managed
dependencies, and that is also