Can anyone explain to me why maven does not display all the actions that is
being performed on each of the projects during a multiproject? It seems to
only display the actions for the first project. example:
maven -Dgoal=clean,jar:install multiproject:goal
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT
Starting the reactor...
Our processing order:
Utility Component
properties Component
exceptionHandler Component
keyUtility Component
microstrategy Component
+----------------------------------------
| Executing clean,jar:install Utility Component
| Memory: 2M/3M
+----------------------------------------
multiproject:goal:
clean:clean:
[delete] Deleting directory
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target
clean:
java:prepare-filesystem:
[mkdir] Created dir:
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target/classes
java:compile:
[echo] Compiling to
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target/classes
[javac] Compiling 53 source files to
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target/classes
java:jar-resources:
test:prepare-filesystem:
[mkdir] Created dir:
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target/test-cl
asses
[mkdir] Created dir:
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target/test-re
ports
test:test-resources:
test:compile:
[javac] Compiling 46 source files to
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/utility/target/test-cl
asses
test:test:
[junit] dir attribute ignored if running in the same VM
[junit] Running com.nielsenmedia.db.DBUtilitiesTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.03 sec
[junit] dir attribute ignored if running in the same VM
[junit] Running com.nielsenmedia.db.NonPooledDataSourceTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.029 sec
/dun/d2drt1/devel/hahnerd/java/JavaProjects/npowerApp/microstrategy/src/java
/com/nielsenmedia/npower/mstr/MicroStrategySearch.java:33: cannot resolve
symbol
symbol : class MicroStrategyException
location: package mstr
import com.nielsenmedia.npower.mstr.MicroStrategyException;
16 errors
BUILD FAILED
File...... file:/home/hahnerd/.maven/plugins/maven-multiproject-plugin-1.1/
Element... maven:reactor
Line...... 174
Column.... 9
Unable to obtain goal [java:compile] --
file:/home/hahnerd/.maven/plugins/maven-java-plugin-1.3/:34:48: <ant:javac>
Compile failed; see the compiler error output for details.
Thanks,
\ /
Ron Hahne (* *)
Cube C3C024 ooO( )Ooo
Brooker Creek (813) 366-4052
Cell Phone (727) 638-0690
-----Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 11, 2004 4:37 AM
To: Maven Users List
Subject: Re: Automatically build dependet projects?
The plugin is multiproject.
I suppose you have a directory structure like this :
projects_dir
| -> project A
| -> project B
if you run in projects : maven -Dgoal=clean,jar:install multiproject:goal
All your project are build in correct order.
Emmanuel
----- Original Message -----
From: "Christoph Kiehl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 11, 2004 10:26 AM
Subject: Automatically build dependet projects?
> Hi,
>
> I'm currently trying to integrate maven in our build process. One goal I
> would like to achieve is the following:
>
> There are two projects A and B. B depends on A. So if I build B I would
like
> maven to build A first install the jar in the local repo and then build B
> with the new jar. Is there some functionality like this already available
in
> maven? I already searched the plugin list but could not find a suitable
one.
> Or is it perhaps more efficient to not build A every time B builds, but to
> install As jar manually? How do you handle such dependent projects?
>
> Thanks in advance,
> Christoph
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
