maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From norbertwnuk <>
Subject [GitHub] maven-surefire pull request: SUREFIRE-1136 Mark surefire.forkNumbe...
Date Sat, 31 Jan 2015 09:16:40 GMT
GitHub user norbertwnuk opened a pull request:

    SUREFIRE-1136 Mark surefire.forkNumber feature as not compatible with maven 2.x, unit
test cleanup.


You can merge this pull request into a Git repository by running:

    $ git pull SUREFIRE-1136-build-fix

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #84
commit d6a8af593fc03e12ecf2dc8047669472f7ca263b
Author: norbertwnuk <>
Date:   2015-01-28T01:51:39Z

    SUREFIRE-1136 Current working directory propagation in forked mode - ignore testExceptionWhenCurrentDirectoryCannotBeCreated
under certain conditions.

commit 9a8bb172cae84fe89f597843560056def30bd351
Author: norbertwnuk <>
Date:   2015-01-30T23:38:31Z

    SUREFIRE-1136 Current working directory propagation in forked mode - mark CurrentWorkingDirectoryInForkedModeTest
as not compatible with maven 2.x since ${surefire.forkNumber} expansion cannot work on this


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message