Hi, 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.
In order to do in container testing you should check Cactus. Remember that maven philosophy is "one artifact per project". Carlos Sanchez A Coru�a, Spain Oness Project http://oness.sourceforge.net > -----Original Message----- > From: matthew.hawthorne [mailto:[EMAIL PROTECTED] > Sent: Monday, June 07, 2004 7:26 AM > To: Maven Users List > Subject: I wish there were test:jar and test:jar-install goals > > I frequently find myself in situations where I need a > "test:jar" and "test:jar-install" goal. Sometimes I have set > of fairly abstract tests that the tests in another subproject > depend on. Other times, I have tests that need to be run in > a certain environment (inside of a container), and I need to > war.bundle the test jar into a war. > > Currently, my options for doing this are: > > 1) Do some maven.xml magic to build a test jar whenever the > main jar is built, and install the test jar whenever the main > jar is installed. > > 2) Put the unit tests in a separate project from the classes > that they are testing, so they will be in the sourceDirectory > instead of the unitTestSourceDirectory, and therefore easy to > build and install. > > But, as I've suggested, I think this would be easier if there > were goals to build and install test jars. > > Anyone else agree? > > --------------------------------------------------------------------- > 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]
