On 01/12/2010 3:28 AM, Manuel Bernhardt wrote:
Hi all,
I have the following set-up:
Project
- module A: library (packaged as JAR)
- module B: test webapp (packaged as WAR)
B depends on A via a simple<dependency> declaration.
before migrating to maven, we had a tomcat / jetty set-up where B
would depend directly on the classes of A, so that you could debug&
do modifications on A while running / debugging B and not having to
re-build A.
is there any way to reproduce this? what I'm looking for would be some
kind of "direct module dependency" (i.e. instead of B depending on the
packaged A artifact, it would directly look at its classes) or some
means to tell jetty and tomcat "guys, for that artifact, look at this
path".
Not a good idea.
- No reproducability
- Too many dependencies
- Too difficult for other members of the development to determine what
combination actually works.
You might break A down to smaller more stable libraries.
What do you want to improve by going to Maven?
Ron
Thanks,
Manuel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
