You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:23:22 UTC

[jira] (MPTEST-73) test:test goal results in double invocation of java:compile goal

     [ https://jira.codehaus.org/browse/MPTEST-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MPTEST-73.
--------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> test:test goal results in double invocation of java:compile goal
> ----------------------------------------------------------------
>
>                 Key: MPTEST-73
>                 URL: https://jira.codehaus.org/browse/MPTEST-73
>             Project: Maven 1.x Test Plugin
>          Issue Type: Bug
>    Affects Versions: 1.8.2
>         Environment: All environments
>            Reporter: Alex Volanis
>
> The test:test goal has been modified to conditionally invoke test:compile via attainGoal(test:compile). This was previously done with the prereqs attribute. Doing so caused the java:compile and all pre/post goals associated to fire twice. You can witness this behaviour even when compiling MAven 1.1 from source.
> It seems unnecessary to do this for the test:test goal which conditionally skips the tests when test:compile also conditionally skips compiling. Making the same operation for test:single which intentionally omits the check for maven.test.skip makes a lot of sense.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)