resolve dependencyManagement dependencies from a bill of materials (bom) pom

[Jim Sellers <ji...@gmail.com>]

Hi all.

For the company that I work at we've got a "bill of materials" (bom) pom
that contains dependencies that we know will work together.  Projects will
use the import scope to pull this into their own projects.  However, there
is a possibility of putting in an artifact that won't be resolved by our
corp proxy (archiva).

Does anyone know of a plugin or way when running the a phase of the bom it
will try and resolve and download these dependencies?  That way a mistake
can be found at that stage that something is wrong.

eg. if the pom depends on org.hibernate:hibernate-core:999, you won't see
any issue until the projects that use that pom are built.

Thanks for your time!
Jim

Re: resolve dependencyManagement dependencies from a bill of materials (bom) pom

[Jim Sellers <ji...@gmail.com>]

No goals in the dependency do this as far as I know.  Just for fun I tried
to run all the goals to see if one of them would do it, but they don't.

There is a ticket open for having a "tree" for the dep management section,
and I believe that would work for me.
http://jira.codehaus.org/browse/MDEP-201

Thanks.
Jim


On Wed, May 6, 2009 at 1:44 PM, Thejaswi Narayana <th...@gmail.com>wrote:

>
> I guess the Maven dependency plugin goals do that. Do not remember which
> ones.
>
>
> Jim Sellers wrote:
> >
> > Hi all.
> >
> > For the company that I work at we've got a "bill of materials" (bom) pom
> > that contains dependencies that we know will work together.  Projects
> will
> > use the import scope to pull this into their own projects.  However,
> there
> > is a possibility of putting in an artifact that won't be resolved by our
> > corp proxy (archiva).
> >
> > Does anyone know of a plugin or way when running the a phase of the bom
> it
> > will try and resolve and download these dependencies?  That way a mistake
> > can be found at that stage that something is wrong.
> >
> > eg. if the pom depends on org.hibernate:hibernate-core:999, you won't see
> > any issue until the projects that use that pom are built.
> >
> > Thanks for your time!
> > Jim
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/resolve-dependencyManagement-dependencies-from-a-bill-of-materials--%28bom%29-pom-tp23164670p23411964.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
>
>

Re: resolve dependencyManagement dependencies from a bill of materials (bom) pom

[Thejaswi Narayana <th...@gmail.com>]

I guess the Maven dependency plugin goals do that. Do not remember which
ones. 


Jim Sellers wrote:
> 
> Hi all.
> 
> For the company that I work at we've got a "bill of materials" (bom) pom
> that contains dependencies that we know will work together.  Projects will
> use the import scope to pull this into their own projects.  However, there
> is a possibility of putting in an artifact that won't be resolved by our
> corp proxy (archiva).
> 
> Does anyone know of a plugin or way when running the a phase of the bom it
> will try and resolve and download these dependencies?  That way a mistake
> can be found at that stage that something is wrong.
> 
> eg. if the pom depends on org.hibernate:hibernate-core:999, you won't see
> any issue until the projects that use that pom are built.
> 
> Thanks for your time!
> Jim
> 
> 

-- 
View this message in context: http://www.nabble.com/resolve-dependencyManagement-dependencies-from-a-bill-of-materials--%28bom%29-pom-tp23164670p23411964.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