[ http://jira.codehaus.org/browse/MECLIPSE-164?page=all ]
Francois Loison updated MECLIPSE-164:
-------------------------------------
Attachment: project-25.zip
New files for automatic class folders test.
Unzip into src/resources/test/projects
> class folders not handled
> -------------------------
>
> Key: MECLIPSE-164
> URL: http://jira.codehaus.org/browse/MECLIPSE-164
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: dependency resolution
> Affects Versions: 2.2
> Reporter: Francois Loison
> Assigned To: Kenney Westerhof
> Attachments: MNG-164-maven-eclipse-plugin.patch,
> MNG-164-TEST-maven-eclipse-plugin.patch, patch.classfolder.txt, project-25.zip
>
>
> 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 folders.
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
