• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dealing with maven transitive dependencies
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dealing with maven transitive dependencies


  • Subject: Re: Dealing with maven transitive dependencies
  • From: Frédéric JECKER <email@hidden>
  • Date: Wed, 17 Mar 2010 23:17:34 +0100

Hi Henrique

Thanks for the hint, dependency:analyze is exactly what I was looking for !

Regards

Fred

Le 17 mars 2010 à 17:48, Henrique Prange a écrit :

> Hi Frédéric,
>
> You can use the Maven dependency plug-in to analyze your pom and check which dependencies are required but not declared. Just run the following command:
>
> mvn clean dependency:analyze
>
> Cheers,
>
> Henrique
>
> On 17/03/10 13:30, Frédéric JECKER wrote:
>> Hi,
>>
>> Sorry for the little off-topic post, but maybe if I'm lucky, someone on
>> the list already solved the problem.
>> So I'm mavenizing a huge app with a lot of frameworks.
>> Some of them are core frameworks other frameworks rely on.
>> i.e :
>> Framework A depends on commons-lang
>> Framework B depends on Framework A and also on commons-lang
>>
>> If in the pom of Framework B I omit to declare the dependency on
>> commons-lang, the framework will compile without complaining
>> because at compile time, commons-lang will be provided by Framework A.
>> This works nice but, I'd like my sub-pom to be the more precise as
>> possible so that they declare every dependency they need.
>> The problem is that with 42 frameworks to mavenize I'm going nuts.
>> I'd like to configure maven to ignore transitive dependencies so that if
>> a sub-pom is incomplete the build fails.
>>
>> I tried to disable the transitive dependencies using the following
>> configuration but it doesn't seem to work :
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-dependency-plugin</artifactId>
>> <executions>
>> <execution>
>> <id>resolve</id>
>> <phase>compile</phase>
>> <goals>
>> <goal>resolve</goal>
>> </goals>
>> <configuration>
>> <excludeTransitive>true</excludeTransitive>
>> </configuration>
>> </execution>
>> </executions>
>> </plugin>
>>
>> Thanks for your help
>>
>> Fred
>>
>>
>>
>>  _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Dealing with maven transitive dependencies (From: Frédéric JECKER <email@hidden>)
 >Re: Dealing with maven transitive dependencies (From: Henrique Prange <email@hidden>)

  • Prev by Date: Re: Dealing with maven transitive dependencies
  • Next by Date: Re: Dealing with maven transitive dependencies
  • Previous by thread: Re: Dealing with maven transitive dependencies
  • Next by thread: Browser handling a URL having .123. in the breadcrumb trail as a Lotus file
  • Index(es):
    • Date
    • Thread