Brett Porter wrote:
Your advice is sound. Hmm, it's not neccessarily better. It'll be more congrous with the past. Conservatism, as in politics, often serves those who have grown used to a system.Yes, sharing a classes directory will work, but you haven't answered the reason why you think this is better :)
Not sure what app server you use. I'm using JBoss and Jboss does not distinguish between the jar file app-gui.jar and a directory named app-gui.jar, as long as the directory matched the jar's layout. So when developing, we never bother to jar.
So the way I see it, I can:
1) copy over all the classes for all the subprojects to one central directory - jboss/server/myapp/deploy/app-gui.jar/com/...
set every project's classpath to jboss/server/myapp/deploy/app-gui.jar
2) compile to maven_project/target/classes/com...
set every project's classpath to the point to it's dependencies' targets (ie set app-gui's compile classpath to ../app-lib/target/classes
Now, do you know how you do this? Add additional directories to the java:compile classpath?
-Randy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
