[
https://jira.codehaus.org/browse/MECLIPSE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-164.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> class folders not handled
> -------------------------
>
> Key: MECLIPSE-164
> URL: https://jira.codehaus.org/browse/MECLIPSE-164
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.2
> Reporter: Francois Loison
> Assignee: 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 was sent by Atlassian JIRA
(v6.1.6#6162)
