[ http://jira.codehaus.org/browse/MPTEST-66?page=comments#action_73022 ] nicolas de loof commented on MPTEST-66: ---------------------------------------
Lot's of code generation plugin are attached to java:compile as preGoals... I can suggest two options : 1. keep previous behaviour and assume test:* allways depends on java:compile, even if this is not clean. 2. make ONLY the "test" goal (not the "test:test") depend on java:compile, so that a - "maven test" compiles project and run the tests, as any user may expect it - any plugin depending on test:test will NOT force a twice compilation. This 2d solution requires update to other plugins. Any 3d solution would be welcome as both seems not very cool... > 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 > Fix For: 1.8.1 > > 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
