You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Thomas Van de Velde (JIRA)" <ji...@codehaus.org> on 2005/03/17 14:56:44 UTC

[jira] Created: (MPECLIPSE-83) Incorrect maven.eclipse.classpath.include handling

Incorrect maven.eclipse.classpath.include handling
--------------------------------------------------

         Key: MPECLIPSE-83
         URL: http://jira.codehaus.org/browse/MPECLIPSE-83
     Project: maven-eclipse-plugin
        Type: Bug
    Versions: 1.9    
    Reporter: Thomas Van de Velde
     Fix For: 1.10


When adding additional projects to the classpath, the plugin transforms the source paths to a path relative to the machine's root.  E.g. when you define:

maven.eclipse.classpath.include=/ProjectA

The plugin generates:

<classpathentry kind="src" path="/ProjectA"/>

This is not the desired behavior!

It should generate:

<classpathentry kind="src" path="C:/ProjectA"/>

To get the desired behavior I had to patch classpath.jelly:



<!-- add extra directories to be included in the classpath -->
  <j:forEach var="res" items="${maven.eclipse.classpath.include.split}">
    <!--maven:makeRelativePath var="srcDir" basedir="${basedir}" path="${res}"  separator="/"/-->
    <classpathentry kind="src" path="${res}"/>
  </j:forEach>

-- 
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org