Resources are added as path even if they do not exist in the filesystem
-----------------------------------------------------------------------
Key: MPECLIPSE-81
URL: http://jira.codehaus.org/browse/MPECLIPSE-81
Project: maven-eclipse-plugin
Type: Bug
Versions: 1.9
Reporter: Felipe Leme
If the property maven.eclipse.resources.addtoclasspath is set to true and the
resources directory is defined in the POM but does not exist in the filesystem,
the generated .classpath will cause Eclipse to fail.
A quick fix is to just put an <u:available> at classpath.jelly, from:
<maven:makeRelativePath var="resourceDirectory" basedir="${basedir}"
path="${resource.directory}" separator="/"/>
<!-- don't add duplicate directories -->
<j:if test="${!resourceDirectory.equals(srcDir) and
<!-- .... -->
</j:if>
to:
<maven:makeRelativePath var="resourceDirectory" basedir="${basedir}"
path="${resource.directory}" separator="/"/>
<!-- don't add duplicate directories -->
<u:available file="${basedir}/${resourceDirectory}">
<j:if test="${!resourceDirectory.equals(srcDir) and
<!-- .... -->
</j:if>
</u:available>
I will not commit such fix yet though, as we need a more robust solution, like
checking that the file is really a directory, adding a new testcase and making
sure the same problem does not occurr for regular resources.
-- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
