You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/07/24 22:55:22 UTC

[jira] Closed: (MPTEST-66) 1.8 version introduces bug in other plugins

     [ http://jira.codehaus.org/browse/MPTEST-66?page=all ]

Lukas Theussl closed MPTEST-66.
-------------------------------

      Assignee: Lukas Theussl
    Resolution: Won't Fix

It seems more logical to fix this in the war plugin. There is a slight backwards compatibility problem, but it only affects the case when test.skip=true, which is not recommended anyway (certainly not in production builds!).

> 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