When trying to access test resources in my unit tests, maven 2.0.8 and above
are returning the wrong directory.
Here is my basic code to access the folder
def file = new JmblXsltDriverTest().getClass().getResource(/)?.file
println file
On 2.0.7 this would print
than helping but I'm sure
your problem lies in whther you compile to the correct output folder or
copy to the correct output folder. Look for filters that may have been
added as well.
jlo_gestalt wrote:
When trying to access test resources in my unit tests, maven 2.0.8 and
above
plugin itself doesn't require this - it's probably one of
the other plugins you have bound. Maven must resolve these plugins to
discover where they fit into the lifecycle, but I'm not sure why it
would be trying to resolve other modules in the project.
- Brett
2008/5/2 jlo_gestalt [EMAIL
.
-Original Message-
From: jlo_gestalt [mailto:[EMAIL PROTECTED]
Sent: Friday, May 02, 2008 10:12 AM
To: users@maven.apache.org
Subject: RE: How to get around maven causing CI to fail
Yes,
that is exactly what I am referring to. Any way we can change this or
provide
I am not sure this is a bug or intentional, but it's very annoying how the
clean phase requires all the dependencies to run. It's annoying because our
CI environment (like everyone else) usually executes mvn clean install.
And if I have a multi module project, when adding a new module, CI fails
