maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Heinz Marbaise <khmarba...@gmx.de>
Subject Re: Copy-dependencies goal error
Date Mon, 05 Oct 2015 22:22:11 GMT
Hi Michael,

I'm replying to Jörg...

Kind regards
Karl Heinz Marbaise


On 10/6/15 12:14 AM, Michael.CTR.Tarullo@faa.gov wrote:
> Karl,
>
> Could you clarify this.  I don't understand your reply.
>
> In fact I'm not sure if you are replying to me or Jorg.
>
> It appears to be the latter.  Could you please confirm?
>
> Thank you.
>
> Michael Tarullo
> Contractor (Engility Corp)
> Enterprise Architect
> NSRR System Administrator
> FAA WJH Technical Center
> (609)485-5294
>
>
> -----Original Message-----
> From: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
> Sent: Monday, October 05, 2015 6:10 PM
> To: Maven Users List
> Subject: Re: Copy-dependencies goal error
>
> Hi,
>
> On 10/5/15 7:51 PM, Jörg Schaible wrote:
>> Hi Michael,
>>
>> Michael.CTR.Tarullo@faa.gov wrote:
>>
>>> My apology about part of this reply.  I did not understand part of
>>> your suggestion.
>>>
>>> I thought you were saying 3.0.5 is the latest release.
>>>
>>> That said, I don't see how using the latest release or an older
>>> release makes any difference.
>>>
>>> I have a requirement to use 3.1.1 from a COTS product vendor, so that
>>> is probably not an option.  And "bogus" is just not a good enough
>>> explanation for me.  What specifically is wrong with what I am doing
>>> that does not work in this release?
>>
>> I just cite my original mail:
>>
>>> IIRC you have problems with 3.1.x when using dependencies with import
>>> scope, because it ignores then your settings then for transitive deps
>>> declaring their own repository in the POM.
>>
>> AFAICS, you are using dependencyManagement with dependencies declared
>> with scope "import"".
>
>
> The given pom does not contain any dependencyManagement...so it does simply plays not
a role here...Apart from that import scope means only to use the dependencyManagement part
and nothing else as described in the documentation...so it does not ignore it nor is it wrong...
>
> See the original documentation
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html.
>
> so this is NOT a problem in contrary it is exactly working as it should be...Apart from
using repository definition in a pom is a bad practice...But this is a different story...
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message