The classpath entry that you see is make resource folders easily visible
in Package Explorer view, i.e. this is pure presentation and no bares
other functionality. All resource copying/filtering is done by Maven. I
wrote brief wiki page [1] that explains integration between maven build
lifecycle and eclipse build.
Also, there were reports that somehow resources get deleted after being
copied to the target folder by Maven, but we were never able to
reproduce and debug the problem. If you can provide sample project and
steps to reproduce the problem, I'd be happy to have a look.
[1] http://docs.codehaus.org/display/M2ECLIPSE/Maven+build+lifecycle
nicolas de loof wrote:
From my understanding, this is forced by m2eclipse to let the maven
builder handle resource filtering and copy to target when some resources
are changed.
2008/7/23 nicolas de loof <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:
Hello,
My eclipse project uses m2eclipse and is configured with :
<classpathentry excluding="**" kind="src"
output="target/classes" path="src/main/resources"/>
The excluding filter has the side effect (on eclipse 3.4) to disable
ANY resource file from beeing copied to the target directory.
Is this the expected behaviour ?
Nicolas
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
