maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Loison (JIRA)" <>
Subject [jira] Updated: (MECLIPSE-164) class folders not handled
Date Tue, 03 Oct 2006 16:51:26 GMT
     [ ]

Francois Loison updated MECLIPSE-164:

    Attachment: patch.classfolder.txt

I fixed issue and attached SVN patch.

-> I changed Config class to add a getClassFolders() method returning depencies which are
class folders (system scope + folder reference)
-> I changed Project writer to created linked resources for class folders
->I changed Classpath writer to add class path entries referencing class folder names (and
not absolute path)

Basic test is OK.
Plese tell me if you accept patch, then I'll add comments verbosity.

> class folders not handled
> -------------------------
>                 Key: MECLIPSE-164
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: dependency resolution
>    Affects Versions: 2.2
>            Reporter: Francois Loison
>         Attachments: patch.classfolder.txt
> I defined in POM a class folder:
> <dependency>
>       <groupId>com.ptc</groupId>
>       <artifactId>wt.codebase</artifactId>
>       <version>1.0</version>
>       <scope>system</scope>
>       <systemPath>c:/dev/java/maven/wdc.ptc/codebase</systemPath>
> </dependency>
> This allows to add c:/dev/java/maven/wdc.ptc/codebase to compile classpath.
> Generated Eclipse .classpath file contains following entry:
>   <classpathentry kind="lib" path="C:/Dev/java/maven/wdc.ptc/codebase"/>
> This entry is failing: Eclipse 3.2 doesn't accept external project folders for class
> To resolve this, I create manually a linked folder in .project and defines class folder
to point on linked folder.
> This may be an hint for resolution.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message