Multiproject jar:install when the jars have never been deployed

[Gareth Cronin <ga...@kiwiplan.co.nz>]

We normally do a "multiproject:jar:install" to build the latest version 
of all our jars/projects using Reactor. This works fine until... we 
increment the version number for all the projects. The multiproject goal 
fails because it can't find the dependencies, but the dependencies are 
exactly what we want the multiproject to build! Is there any way to do 
this without having to manually go through each project in the usual 
Reactor-specified order and do a jar:install?

Thanks,

Gareth.

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

Re: Multiproject jar:install when the jars have never been deployed

[di...@multitask.com.au]

Create a project with no dependencies to be the 'multiproject' project.

This is currently a known failing of maven and the reactor in that 
projects need to have dependencies satisfied before they are processed.
--
dIon Gillard, Multitask Consulting



Gareth Cronin <ga...@kiwiplan.co.nz> wrote on 18/02/2004 07:54:53 AM:

> We normally do a "multiproject:jar:install" to build the latest version 
> of all our jars/projects using Reactor. This works fine until... we 
> increment the version number for all the projects. The multiproject goal 

> fails because it can't find the dependencies, but the dependencies are 
> exactly what we want the multiproject to build! Is there any way to do 
> this without having to manually go through each project in the usual 
> Reactor-specified order and do a jar:install?
> 
> Thanks,
> 
> Gareth.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>