On 5 Jul 2016, at 8:37, Stephen Connolly wrote:
> 1.0 is just a hint, hints can be overridden
> [1.0] is a hard requirement
The later also forces maven to download the metadata, and check the version
exists in said metadata, which - even if its in the repository, but the
meta-data is broken ( a
Am 07/04/16 um 22:46 schrieb Stephen Connolly:
> So when I have a pom with 1.0 that is the strongest hint
> for that pom. That version will be used in that pom even if a transitive
> dependency has 2.0
>
> So one solution to that is to use ranges... if the transitive dependency
> has a version lik
That's my understanding... and if you have two conflicting hard
dependencies for the same artifact with different versions then Maven
should fail the build until you exclude the one you don't want with
exclusions
On 4 July 2016 at 21:42, Christian Schulte wrote:
> Am 07/04/16 um 22:37 schrieb St
Hi,
>>
>> is version "1.0" really different to the version range "[1.0]"? I am
>> asking because I would like to understand what MNG-4883 is about. If you
>> download the attached 'maven-samples.zip' of that issue and build it,
>> Maven will
Am 07/04/16 um 22:37 schrieb Stephen Connolly:
> 1.0 is just a hint, hints can be overridden
By means of dependency mediation? So a "1.0" can be ignored during
dependency mediation due to e.g. the nearest wins strategy eliminating
that "1.0" but a "[1.0]" can never be eliminated by a nearer depend
1.0 is just a hint, hints can be overridden
[1.0] is a hard requirement
On 4 July 2016 at 21:35, Christian Schulte wrote:
> Hi,
>
> is version "1.0" really different to the version range "[1.0]"? I am
> asking because I would like to understand what MNG-4883
Hi,
is version "1.0" really different to the version range "[1.0]"? I am
asking because I would like to understand what MNG-4883 is about. If you
download the attached 'maven-samples.zip' of that issue and build it,
Maven will fail due to "overconstraint version
