Hi!
Just in case someone runs into the same problem; I have now found a
workaround for this. I create two modules that points to the same
directories, one is the normal par or ejb3 module and the other is a jar
module. I include a dependency to the jar module from other modules
during test and I also let the test be executed from the jar module and
totally skip them when building the par and ejb3 modules.
Hope that might help someone else.
--
Regards
Magnus
Magnus Lundgren skrev:
Hi everyone!
New to the list, haven't had the need for direct questions, but right
now I am stuck with a problem that I don't know how to solve.
I have a multi-module project with ejb3, jar, war, par and ear
modules. Everything worked fine uptil now. I can build the whole
application, and it runs without any problems on my JBoss
installation. A few days ago I added some more tests to the code.
These tests belong to one of the ejb3 module, and the code in them are
dependent on another of the ejb3 modules. The source code also has
this dependency and that hasn't been a problem, but now the test code
doesn't get the correct classpath so they cannot compile. After a
little debugging in maven I noticed that the classpath for the test
compilation was made to the actual module i.e the XXXx.ejb3 file in
the repository instead of towards the target/classes directory where
the compiled files are.
So my problem is: How do I get Maven to correctly resolve the
classpath for my test classes, not just my source classes, when I have
a dependency to a ejb3 or par module, from a different module?
--
Regards
Magnus Lundgren
---------------------------------------------------------------------
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]
