Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.19.1
-
None
-
None
Description
The maven failsafe pluging ignores the <classesDirectory> property in versions 2.19.x version 2.18.1 works as expected / documented.
Config:
... <configuration> <classesDirectory>${project.build.directory}/classes</classesDirectory> </configuration> ...
Cmd:
mvn -X clean verify
Output:
2.18.1
[DEBUG] boot classpath:
/home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
/home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
/home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
/home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
...
2.19.1
[DEBUG] boot classpath:
/home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
/home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
/home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
/home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
...
Attachments
Issue Links
- is duplicated by
-
SUREFIRE-1198 Failsafe does not allow to configure the jar file to use
- Closed
- relates to
-
SUREFIRE-1198 Failsafe does not allow to configure the jar file to use
- Closed
-
SUREFIRE-855 Allow failsafe to use actual jar file instead of target/classes
- Closed