RE: Multiple dependencies of different types

[Maczka Michal <mi...@imtf.ch>]

> -----Original Message-----
> From: MichaelH@sptech.com [mailto:MichaelH@sptech.com]
> Sent: Friday, July 23, 2004 4:20 PM
> To: users@maven.apache.org
> Subject: Multiple dependencies of different types
> 
> 
> It would seem that Maven 1.0 does not take the <type> element 
> into account 
> when downloading a dependency.  Is that correct behavior?
> 
> I have a project that's meant to be a master build over a 
> number of other 
> projects.  For example, it downloads a project A's artifact 
> (i.e. a jar 
> file) and then intends to interrogate that A's POM and subsequently 
> download A's dependencies.  So, in the master project's 
> project.xml I've 
> listed its dependencies as:
> 
>         <dependency>
>             <groupId>A</groupId>
>             <artifactId>A</artifactId>
>             <version>2.1.0.2</version>
>         </dependency>
> 
>         <dependency>
>             <groupId>A</groupId>
>             <artifactId>A</artifactId>
>             <version>2.1.0.2</version>
>             <type>pom</type>
>         </dependency>
> 
> 
> Apparently to Maven there's no difference between these two 
> dependency 
> entries even though they are in fact different things: one's 
> a jar file 
> the other is a POM file.  So, Maven only reports a single 
> dependency for 
> that groupId-artifactId when, say, you iterate over the pom.artifacts 
> list.
> 
This is known limitation which soon will be fixed.

Your particual use case will be even built-in into maven: whenever maven
will dowload any artifact
it will download its pom.

Michal

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