You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Renaud Julienne (JIRA)" <ji...@codehaus.org> on 2006/04/03 18:53:44 UTC

[jira] Updated: (MECLIPSE-89) Eclipse plugin should not try to resolve system dependencies paths relatively to project location.

     [ http://jira.codehaus.org/browse/MECLIPSE-89?page=all ]

Renaud Julienne updated MECLIPSE-89:
------------------------------------

    Attachment: MNG-MECLIPSE-89-maven-eclipse-plugin.patch

> Eclipse plugin should not try to resolve system dependencies paths relatively to project location.
> --------------------------------------------------------------------------------------------------
>
>          Key: MECLIPSE-89
>          URL: http://jira.codehaus.org/browse/MECLIPSE-89
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     Versions: 2.2
>     Reporter: Renaud Julienne
>  Attachments: MNG-MECLIPSE-89-maven-eclipse-plugin.patch
>
>
> When a system dependency in located inside the project directory, the eclipse plugin resolves it path relatively to the maven project directory, and uses this relative path  in the generated eclipse project to point the library.
> The problem is that this path is of course resolved by eclipse as a path relative to the eclipse project, which is not if -Declipse.workspace is specified, and so the eclipse project cannot be built.
> System dependencies paths should be handled as absolute paths, or as paths relative to the eclipse project's path.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira