[ http://jira.codehaus.org/browse/MPTEST-66?page=all ]
nicolas de loof reopened MPTEST-66:
-----------------------------------
Please reconsider this issue as not only the WAR plugin get's broken.
+ The JAR plugin will compile the java source two times (beacuse
prereqs="java:compile,java:jar-resources,test:test")
+ The javaapp plugin (from [EMAIL PROTECTED]) doesn't compile java if skip=true
+ maybe other external plugins expect test:test to compile sources, based on
copy/paste of code from official maven plugins, so upgrading to
maven-test-plugin 1.8 can break the build process.
Why not simply adding moving prerequs on java:compile to test:test ?
<goal name="test:test"
description="Test the application"
prereqs="java:compile,java:jar-resources">
> 1.8 version introduces bug in other plugins
> -------------------------------------------
>
> Key: MPTEST-66
> URL: http://jira.codehaus.org/browse/MPTEST-66
> Project: maven-test-plugin
> Issue Type: Bug
> Affects Versions: 1.8
> Reporter: nicolas de loof
> Assigned To: Lukas Theussl
> Attachments: MPTEST-66.patch
>
>
> When maven-war-plugin is run with maven.test.skip=true, the sources are not
> compiled.
> Latest version of test-plugin has removed prereqs on java:compile &
> java:jar-resources.
> Assuming other plugins themself run the java:compile goal may have impact on
> lots of plugin and can break many application builds. I think the "test:test"
> goal may have a prereqs="java:compile,java:jar-resources", and the
> "test:compile" goal only prereqs="test:prepare-filesystem,test:test-resources"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
