Adrian Shum wrote:
Dear all,
I have just installed m2eclipse 0.9.4.20080603 and recent version of
m2Eclipse removed usage of target-eclipse and use maven's
target/ as default output directory of eclipse.  Before m2eclipse
changed to use target-eclipse as default output directory, there is
a problem if I use target/ as default output directory.  Once I do
mvn clean install  in command line maven, it will rebuild all class files,
and once I need to use them in Eclipse (e.g. launching JUnit Test), it
seems to me that Eclipse have done some caching and it detects the
classes are changed, and it refuse to run the tests.  I have to do clean
build in Eclipse again to solve that.  Is the situtation the same in latest
m2eclipse? If so, can I choose to keep on using target-eclipse?
Have just upgraded to Eclipse 3.4 too and I have reimported some maven
projects to my workspace.  I found that in the newly imported projects,
default output directory for resources is target/classes and target/test-classes. For my existing projects, it is src/main/resources and src/test/resources.
I found my JUnit tests no longer be able to load resources in test/resources
(I have some unit tests needs to load Spring's app context xml). It seems to
me that the default output directory cause problem for resources loading
in Eclipse's JUnit tests.  It can be solved by either
1) Removing resources from build path, and add them as Class Folder in Libraries, or
2) Remove the Exclude filter of resources folder in build path.  Eclipse
will then copy the files to target directory (However, everytime I change my resource,
it triggers a lengthy (near 10 second) automatic build)
Can anyone give me some hints on these issues?

I've been fighting with resources today. This is what I came up with:

http://jira.codehaus.org/browse/MNGECLIPSE-707

If you reimported your old project maybe you have the same problem I did.

--
Leszek Gawron

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to