On 1/5/07, Christian Goetze <[EMAIL PROTECTED]> wrote:
Thanks for the tips. I ended up making it its own module and just use
the standard assembly. My thinking is that if it's being distributed, it
isn't really a test anymore. I hope this conforms with the idea of the
test vs main source subtrees...
As a side note, why are you wanting to include a jar with test classes
part of an assembly?
This will create source jars, for the code and the test and they will
be available in the maven repository:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>jar</goal>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
This will create the test classes jar so that other projects can
reference these classes, e.g. shared test code.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
Generally you would want to include source only in an source assembly
- so people can build their own. In a binary assembly you dont care
about the test classes.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
