On the risk of asking an Eclipse question rather than a Maven/Eclipse
question... ;-)
First a little preamble, sorry for that!
The goal eclipse:m2eclipse suggests that it will prepare projects for use
within Eclipse. This is the resulting .classpath:
<classpath>
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="src" path="src/main/resources"
excluding="**/*.java"/>
<classpathentry kind="src" path="src/test/java"/>
<classpathentry kind="src" path="src/test/resources"
excluding="**/*.java"/>
<classpathentry kind="output" path="target-eclipse/classes"/>
...
JDT (by design, as I understand) proposes the following so that it won't
mess up resources while processing them into the target folder:
<classpathentry excluding="**" kind="src"
output="src/main/resources" path="src/main/resources"/>
<classpathentry excluding="**" kind="src"
output="src/test/resources" path="src/test/resources"/>
...
Instead, Eclipse will add src/main/resources to the classpath while running
the application.
While I run my application, the classpath looks as follows:
"C:\Program Files\Java\j2sdk1.4.2_14\bin\javaw.exe"
-classpath C:\SVN_WA\workspace\test\target-eclipse\classes
C:\SVN_WA\workspace\test\src\main\resources
If I use eclipse:m2eclipse, I'll end up having the same resources inside
both these run-time classpaths, with the subsequent problems.
So: should I not use eclipse:m2eclipse?
How does it relate to the Maven/Eclipse integration?
Can't I disable that Eclipse adds src/main/resources to the classpath?
With eclipse:m2eclipse it seems to be promoted not to commit .classpath and
.project to SCM; how about commiting when using the Maven/Eclipse
integration?
Thanks for the information that you can give me on this matter.
--
View this message in context:
http://www.nabble.com/src-main-resources-revisited-tp18412792p18412792.html
Sent from the Maven Eclipse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
