If you are using test utilities and superclasses in different projects (as I do) you should add them to src/java dir as any other utility classes. This way they will be packed when calling jar plugin.
True, but I'd want to do it in a different subproject then, and have the 2 side-by-side, like:
myproject/
src
myproject-tests/
srcI don't want my main code and test code in the same source tree, since I only want the test classes if I'm running tests.
In order to do in container testing you should check Cactus.
I spent some time looking at Cactus before. I didn't really like how the Maven plugin wanted
to start and stop my server. Maybe I need to study it a bit more.
But at a glance, it didn't really solve my problem. I can run my tests in the container
fine, my problem is the slightly ugly magic I have to go through in order to get my tests deployed.
From what I remember, Cactus helps with this, but the communication channels with the
app server are always the tough part.
Remember that maven philosophy is "one artifact per project".
If it violates this philosophy then I can see why others would be against it.
However, I consider the tests to be a quasi-artifact, and adding a goal to produce or
install a test jar seems to be trivial.
But you can also do 'maven jar war ear' and get 3 artifacts right there, all derivations of
the same core source tree, so I find this type of situation a bit cloudy.
Thanks for your response.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
