We are running into some issues with unit tests finding the correct working
folder. The root of the problem seems to be that maven uses the root path of
where ever it is launched from. This means that a test coded to create a file
in ./target will sometimes drop that file in the parent's target folder. It
generally works, but it leaves "droppings" all over the source tree. Is there a
way that we can access some maven properties from within the test (in java)
that could be used to refer to the correct location. I'm specifically
interested in ${project.build.directory} but others would be handy. I'm hoping
that our tests are running inside the same vm and we can access some property.
The only thing I can think of currently is to use a filtered property file that
is read by the tests, but when you have 100's of modules, this will be
combersome.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
