Hi.
I am using maven-jar-plugin to build test dependencies with goal
'test-jar' like shown below.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
This gives me myArtifactId-1.0-SNAPSHOT-tests.jar in addition to
myArtifactId-1.0-SNAPSHOT.jar
Artifacts using this dependency is then configured like this
<dependency>
<groupId>myGroupId</groupId>
<artifactId>myArtifactId</artifactId>
<version>1.0-SNAPSHOT</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
<dependency>
<groupId>myGroupId</groupId>
<artifactId>myArtifactId</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
For some reason my test dependencies is not included correctly in the
testclasspath every time. While 'mvn -X test' shows correct classpath
the result is another thing. One artifact may build correct one time and
the next time not. In a sequence of builds (parent level) failure can
happen at different artifacts each time (without me changing anything in
between). Build once more and maybe one step further or maybe one step
back. The more artifacts we add to the build process the more hard it
becomes to have a successfully build in sequence.
For the record. My xxx-tests.jar artifacts does contain the correct
content in the repository. Or else it would not be possible to have
successfully builds for some artifacts and not others in one build.
The strange thing and my question is, why does this not work for every
artifact/module every time??
-Ronny
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
