[ http://jira.codehaus.org/browse/MECLIPSE-164?page=comments#action_77512 ] Francois Loison commented on MECLIPSE-164: ------------------------------------------
Thanks for review and encouragements! 1) done 2) not done I didn't understand your direction. 3) done with warning I did a new method for the check called setClassFolder() , however this new method is called from setDeps() Class folder list is derived from deps so it makes sense to compute it from deps setter. 4) Not done I didn't understand your direction. Regards, François > 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, 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 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
