Awesome Christian, it's much better now.
Thank you!
On Wed, Sep 14, 2016 at 3:48 PM, Christian Schulte wrote:
> Am 09/14/16 um 13:50 schrieb Stephane Nicoll:
> > Dependency 'org.springframework.cloud:spring-cloud-commons:jar' has
> > conflicting dependency management from '
> > org.springframew
Am 09/14/16 um 13:50 schrieb Stephane Nicoll:
> Dependency 'org.springframework.cloud:spring-cloud-commons:jar' has
> conflicting dependency management from '
> org.springframework.cloud:spring-cloud-consul-dependencies:1.0.2.RELEASE' and
> 'org.springframework.cloud:spring-cloud-commons-dependenci
Am 09/14/16 um 14:17 schrieb Christian Schulte:
> Am 09/14/16 um 13:50 schrieb Stephane Nicoll:
>> Well, first of all I have no idea what the following means:
>>
>> rearrange the causing imports in the inheritance hierarchy to apply
>> standard override logic based on artifact coordinates.
>
> App
Am 09/14/16 um 13:50 schrieb Stephane Nicoll:
> Well, first of all I have no idea what the following means:
>
> rearrange the causing imports in the inheritance hierarchy to apply
> standard override logic based on artifact coordinates.
Apply inheritance override logic to resolve the conflict. Yo
Hi,
I don't think we agree at all on most of this stuff, fine, I won't
press it. However...
On Wed, Sep 14, 2016 at 2:42 AM, Stephane Nicoll
wrote:
> First of all, I'd like the error message to change. I still don't know to
> this day what it means. Second, if Maven is able to find out that two
On Wed, Sep 14, 2016 at 1:32 PM, Christian Schulte wrote:
> Am 09/14/16 um 08:42 schrieb Stephane Nicoll:
> > First of all, I'd like the error message to change. I still don't know to
> > this day what it means. Second, if Maven is able to find out that two
> boms
> > provide dependency managemen
Am 09/14/16 um 08:42 schrieb Stephane Nicoll:
> First of all, I'd like the error message to change. I still don't know to
> this day what it means. Second, if Maven is able to find out that two boms
> provide dependency management for foo with conflicting versions, It would
> be nice to say in whic
On Wed, Sep 14, 2016 at 4:51 AM, jieryn wrote:
> Maybe it is different for Spring than for Arquillian, but with
> Arquillian, they will (imho) correctly import a bom inside another
> bom, and sometimes those get out of sync. So if I import the latest
> arquillian:bom and the latest arquillian-tra
Maybe it is different for Spring than for Arquillian, but with
Arquillian, they will (imho) correctly import a bom inside another
bom, and sometimes those get out of sync. So if I import the latest
arquillian:bom and the latest arquillian-transaction:bom, the
arquillian-transaction:bom might refere
On Tue, Sep 13, 2016 at 2:50 PM, jieryn wrote:
> I reported this for Arquillian, earlier...
> https://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%
> 3CCAArU9ia0C7bdvHEMTX3BU%3DChnrb-_chtw8N3xokvKO2_
> Rnzf1A%40mail.gmail.com%3E
>
> Arquillian also follows that style of multiple type=
I reported this for Arquillian, earlier...
https://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%3CCAArU9ia0C7bdvHEMTX3BU%3DChnrb-_chtw8N3xokvKO2_Rnzf1A%40mail.gmail.com%3E
Arquillian also follows that style of multiple type=bom concentrators
which are recommended practice. Even though
11 matches
Mail list logo
