maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shinobu Kawai (JIRA)" <>
Subject [jira] Commented: (MPTEST-66) 1.8 version introduces bug in other plugins
Date Tue, 22 Aug 2006 00:07:49 GMT
    [ ] 
Shinobu Kawai commented on MPTEST-66:

I like nicolas' solution for backward compatability, but I'm not sure if it is "right" to
assume that test:test will always compile and copy resources.  If other plugins need the java:compile
and java:jar-resouces to be run, I think it should explicitly state that, like the JAR plugin
example given.  (Having said that, I don't like the idea of compiling twice, either...)

> 1.8 version introduces bug in other plugins
> -------------------------------------------
>                 Key: MPTEST-66
>                 URL:
>             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:
For more information on JIRA, see:


View raw message