You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildr.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/07/06 10:20:21 UTC

[jira] [Commented] (BUILDR-584) eclipse plugin should use absolute path

    [ https://issues.apache.org/jira/browse/BUILDR-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060391#comment-13060391 ] 

Hudson commented on BUILDR-584:
-------------------------------

Integrated in Buildr-ci-build #235 (See [https://builds.apache.org/job/Buildr-ci-build/235/])
    

> eclipse plugin should use absolute path
> ---------------------------------------
>
>                 Key: BUILDR-584
>                 URL: https://issues.apache.org/jira/browse/BUILDR-584
>             Project: Buildr
>          Issue Type: Bug
>            Reporter: Alexis Midon
>         Attachments: BUILDR-584.patch
>
>
> When a project depends on non-maven artifacts, the Eclipse plugin create a classpathEntry with a relative path. This is wrong. The path should be absolute.
> "Returns the path of this classpath entry. The meaning of the path of a classpath entry depends on its entry kind:
> Source code in the current project (CPE_SOURCE) - The path associated with this entry is the ABSOLUTE path to the root folder."
> See http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/class-use/IClasspathEntry.html
> Also, for some reasons, the directory dependencies are added as sources. This does not make much sense since they are defined as dependencies.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira