the order is defined by dependencies. You need to run an :install goal
(eg jar:install) for the dependency to be put into the local repo
though).
eg. if B depends on A, A will always be built first. As long as the
goal you run installs it to the local repository, B will be able to
find the correct version of A. It will not read A's target directory
for the built JAR though.
- Brett
On Sun, 7 Nov 2004 18:56:59 -0500, Louis Burroughs
<[EMAIL PROTECTED]> wrote:
> I am tring to build an ear file using Maven. I have subprojects to build
> 2 war files and an ear file. The ear file has dependencies on the 2 war
> files. When I execute using reactor, maven executes the subprojects in
> the order it finds them(alphabetically my ear subproject comes first)
> instead of based upon the dependency chain. Beacuse the subprojects have
> not yet been installed in the repository, the build fails.
>
> Here is my maven.xml
>
> <?xml version="1.0"?>
> <project default="ipm:build-all" xmlns:j="jelly:core"
> xmlns:maven="jelly:maven">
> <goal name="ipm:build-all">
> <maven:reactor basedir="${basedir}" includes="*/project.xml"
> goals="ipm-dist" banner="Building" ignoreFailures="false"/>
> </goal>
> </project>
>
> Can someone explain to me how reactor determines the build order ?
>
> ps- I am not familiar with werkz, I know there's a dependency there, but I
> have no idea whta it is
>
> Thanks
> Louis M. Burroughs III
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
