[
https://jira.codehaus.org/browse/SUREFIRE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356168#comment-356168
]
Tibor Digana commented on SUREFIRE-514:
---------------------------------------
@Dan
This wouldn't be safe enough to skip tests upon timestamp changes because the
POM configuration may change the behavior of your tests as well and maybe
system settings would influence the tests as well.
It's better for us not to introduce a new configuration parameter at the
moment. So if you don't necessarily require this feature in SUREFIRE 2.x and
3.0 anymore, we can close it.
> Provide a way to skip a project's tests if nothing has changed
> --------------------------------------------------------------
>
> Key: SUREFIRE-514
> URL: https://jira.codehaus.org/browse/SUREFIRE-514
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Dan Fabulich
>
> Surefire should have an "incremental" mode, perhaps enabled by default.
> We should check the timestamps of every element of the classpath (and every
> class in any classpath folder) and touch a file in "target" with that
> timestamp. If none of those files have been updated, skip tests for the
> current project.
> It definitely needs to be possible to turn this feature off, though, because
> sometimes you need to re-run tests based on external resources not on the
> classpath: deployed web servers, database schema changes, etc.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
