Oops, badly formatted email
Just to clarify - say Subproject B depends on Subproject A.
I would set the classpath of a subproject B to point to the /target/classes directory of subproject A.
Then run 'multiproject:goals' with the goal of 'java:compile'. This should compile all classes without creating jars right? What I'd like to do is have the project in a state where a change to a single class can be deployed and tested by just compiling that class then moving it to the application server directory.
-Randy
Randy Xu wrote:
Hmm... you sure it involves copying files around. I was planning on setting the output classes directories (subproject/target/classes) in the classpath of higher-level subprojects.
Then, I'd run multiproject:goal with -Dgoal=java:compile? Any reason this wouldn't work?
Would this involve overwriting the default java:compile goals? I guess what I'm asking is how one can add directories to the default compile classpath.
-Randy
Brett Porter wrote:
The only way would be to copy class files around, but its not recommended.
Jarring doesn't take very much time at all and makes everything a lot cleaner.
If Jarring takes time, is it really that the test step in between java:compile and jar:jar is slow?
This is a separate problem - there are ways to disable tests for development, but its also highly recommended you run them if they are effective. If they are slow, perhaps you have some integration or performance tests in there and should split them into special integration test projects that can be run before releases instead of every build.
- Brett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
