[
http://jira.codehaus.org/browse/SUREFIRE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich closed SUREFIRE-416.
---------------------------------
Resolution: Fixed
Fixed revision 606809.
> Forked process inherits user.dir of parent process, multimodule builds behave
> differently from single module
> ------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-416
> URL: http://jira.codehaus.org/browse/SUREFIRE-416
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Reporter: Dan Fabulich
> Fix For: 2.4
>
>
> Make a test that depends on the user.dir system property (the current working
> directory), and put in a multimodule reactor.
> When you launch the tests from the reactor, user.dir will be the reactor
> aggregator root. When you launch the tests from the individual module,
> user.dir will be the child's root.
> Brett and I had a conversation about this on IRC. Ideally, we want user.dir
> to have the same default regardless of whether you're running in a reactor or
> not, and whether you're forking or not. We might wish that were the behavior
> of 2.3, but if not, we'll have to change the behavior to make the tests
> behave more logically.
> To solve this, we're going to set user.dir to be ${basedir} when forking;
> when not forking we'll temporarily change the global system properties, and
> finally change them back. (This should be part of a more general test of
> systemProperties when not forking.)
--
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
