Hi,
thanks for the answer
> Not a good idea.
> - No reproducability
I'm not sure what you mean by this
> - Too many dependencies
Actually it's just one dependency, just that it's not depending on a
packaged JAR but on a directory.
> - Too difficult for other members of the development to de
> 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.
You can probably replicate this experience in Eclipse with m2e... or
possib
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 declaration.
before migrating to maven, we had a tomcat / jetty set-up where B
would depend
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 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 d
