[
http://jira.codehaus.org/browse/MPTEST-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100981
]
Alex Volanis commented on MPTEST-73:
------------------------------------
I read MPTEST-66 5 minutes after I submitted the report :(
I patched the plugin to restore the previous behavior in our build environment
since it was causing quite a bit of upset users having lengthy java:compile
preGoals taking too much time in their builds. We have some expensive
java:compile preGoals firing for every project in a mutlicomponent environment
which is causing a lot of wasted time.
If the attainGoal allowed for session propagation this would have never been an
issue. Why doesn't it? I am considering a patch to control this behavior
globally and by tag attribute.
> test:test goal results in double invocation of java:compile goal
> ----------------------------------------------------------------
>
> Key: MPTEST-73
> URL: http://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 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
