maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: Some questions about "grouped dependencies"
Date Wed, 17 Feb 2010 06:02:08 GMT
a) This is the limitation/drawback of grouped dependencies. The dependencies
you get through a grouped dependencies will be a level down (actually they
will be transient deps). Thus, the dependency:analyzer will report false
(not technically though) errors.

/Anders

On Tue, Feb 16, 2010 at 23:43, lukewpatterson <lukewpatterson@gmail.com>wrote:

>
> Some questions about "grouped dependencies" [1]:
>
> a) Should dependencies introduced through "grouped dependencies" be
> considered first-order dependencies?  In the description of a grouped
> dependency pom project: "You can ... add this project as a dependency and
> all of its dependencies will be added to your project."  The
> dependency:analyze goal doesn't seem to understand grouped dependencies.
> The "used undeclared" list can contain entries from the grouped dependency
> project.
>
> b) How can I get the "nearest" non-pom artifacts from MavenProject?  e.g.
> I'd like to get the jars that this project directly depends on, and any
> jars
> that are directly listed in the grouped dependencies
>
>
> Thanks
>
>
> [1]
>
> http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html#pom-relationships-sect-grouping-deps
> --
> View this message in context:
> http://old.nabble.com/Some-questions-about-%22grouped-dependencies%22-tp27615566p27615566.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message