[ http://jira.codehaus.org/browse/MSUREFIRE-4?page=comments#action_70325 ] Brill Pappin commented on MSUREFIRE-4: --------------------------------------
I fully believe that there is a good reason for it (I'm using it after all, and trust the people building it for the most part). However I can tell you this issue has caused me no end of grief in reactor builds. Latest problem: we have a situation where we're using "special" modules for doing QA testing (Acceptance, Regression etc.) and have to run the test from multiple locations, pointing at multiple hosts. Of course there is no easy way to do this sort of thing, but we've settled on simple property files for each module and can switch out the configuration as needed... of course the property files are located in each module under src/main/config (relative to the module). Along comes reactor (combined with/without Continuum) and we can no longer rely on the configuration for any particular module being where we expect it. For the moment we've settled on the less than ideal method of using an absolute path on all machines that we maintain independently. However I would request that if not the default, module relative path options should be added so that the modules resources can be found regardless of the build environment. The standard "build-anywhere" architecture is in my mind, one of the better features of the Maven concept. I have no doubt that it will require a bit of thinking, and I would be very happy to help define the new feature stories if help is wanted. > Testing from a parent POM fails, since current work directory is no longer > the basedir of the subproject > -------------------------------------------------------------------------------------------------------- > > Key: MSUREFIRE-4 > URL: http://jira.codehaus.org/browse/MSUREFIRE-4 > Project: Maven 2.x Surefire Plugin > Issue Type: Bug > Reporter: Joerg Schaible > Assigned To: Brett Porter > > When testing from the parent POM dir, all paths are relative to it. This > causes major trouble in unit tests, that access the file system. All tests > work if the test is started from the subproject directly. In M1 the current > work directory was always ${basedir}. Might be related to MNG-1471. -- 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
