[ 
https://jira.codehaus.org/browse/SUREFIRE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356214#comment-356214
 ] 

Tibor Digana commented on SUREFIRE-1118:
----------------------------------------

Any objections to close this issue as a duplicate to SUREFIRE-514?
Christian, I would appreciate description of this issue copied into 
SUREFIRE-514. It is really good example in your post, but tracking 150 bugs in 
SUREFIRE takes time and we (3 people in project) are not able to complete these 
issue within single release. After year I have finally decided in release 2.18 
and development of 2.19 to make a cleanup in JIRA; otherwise we would be able 
doing it in next ten years.

> Update surefire to not run any tests, if nothing has changed.
> -------------------------------------------------------------
>
>                 Key: SUREFIRE-1118
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1118
>             Project: Maven Surefire
>          Issue Type: Wish
>          Components: Maven Surefire Plugin
>            Reporter: Christian Schulte
>
> Just like the 'maven-compiler-plugin' does not re-compile unchanged source 
> code files
> {code}
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) ---
> [INFO] Nothing to compile - all classes are up to date
> {code}
> {code}
> [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) ---
> [INFO] Nothing to compile - all classes are up to date
> {code}
> The 'maven-surefire-plugin' should not re-run any tests, if nothing has 
> changed.



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

Reply via email to