[ http://jira.codehaus.org/browse/MSUREFIRE-130?page=comments#action_66913 ]
Richard van der Hoff commented on MSUREFIRE-130: ------------------------------------------------ > if we were to do this, then the tests would behave differently based on > whether it were in a multi-module or run from the individual project. They do already, if forkMode==never. > The way it is, the individual project is always consistent, it's only the > fork modes which aren't. I'm not sure that's the case. Anyway, it's certainly true that you can't have it be intuitive both ways. I happen to think that leaving user.dir alone would be the lesser of two evils, but I'm not really that worried about it. > Setting forkMode changes user.dir for multimodule projects > ---------------------------------------------------------- > > Key: MSUREFIRE-130 > URL: http://jira.codehaus.org/browse/MSUREFIRE-130 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > Reporter: Richard van der Hoff > Priority: Minor > > > The working directory of tests on a submodule in a multimodule project is > different dependeng on whether forkMode is enabled or not. > When forkMode==never, the working directory is that of the top-level module; > otherwise, it is set to the directory of the submodule. > I know this is defined behaviour - but it has been suggested that it is > unintuitive. -- 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
