[
https://jira.codehaus.org/browse/SUREFIRE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356181#comment-356181
]
Tibor Digana commented on SUREFIRE-514:
---------------------------------------
No, I don't say that it's a bad feature. I would like to use it as well (in
specific Maven profile due to not enabling this feature by default for safety
reasons but that's a detail in my work).
We have a little problem in the project that we would like to release surefire
3 where the configurations are soft-coded in Java by yourself. It is a big
change and therefore new configuration parameters don't simplify the future
major release.
You can still provide a patch in GitHub. The patches can be forgotten in JIRA.
> 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)
