Well I can certainly start playing with my build properties, however I
was under the impression that the m2eclipse plugin was managing those.
So if I start changing the setting's there am I going down the road
where I could confuse the plugin and subsequently break it in my
environment?
Xavier Coulon wrote:
John,
Did you check the project's 'java build path' properties in Eclipse ?
You can specify the target directory for each source folder defined in
your build path.
You can also check the 'allow output folder' option to specify an
output forlder for each source folder, thus making a clean separation
between main resources and test resources.
For instance, you could set the target directory as 'target/classes'
for your main resources (java classes + properties), and
'target/test-classes' for your test classes (junit, etc..) and their
resources (properties, test data, etc..).
Hope this helps.
Regards,
Xavier
On 1/8/07, *John Towell* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
I just started using m2eclipse plugin and Maven recently. I like the
idea of it very much. One issue I just noticed is it seems that my
<testResources> are not being copied over to the "target" directory by
eclipse build. This would be preferred because I still want to build
and run my unit tests from eclipse. Right now my workaround is to
do a
maven "test-compile" to get the changes copied over and then run the
tests. This is easy to forget however.
Am I not configuring something correctly perhaps? I would
*really* like
to run my unit tests from eclipse, so I hope the answer is not to
run my
tests from maven.
I apologize if this issue has already been discussed, I did search the
archive.
Thanks!
-John
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
