[ http://jira.codehaus.org/browse/MNG-1076?page=comments#action_48740 ]
John Casey commented on MNG-1076: --------------------------------- Well, the approach will work. However, a cleaner approach is to use the artifact.getScope() method to determine whether to treat the dependency as an external library or not. I've got this implemented, and will commit soon. > incorrect classpath entry is generated when dependency has > <scope>system</scope> and <systemPath/> is absolute > -------------------------------------------------------------------------------------------------------------- > > Key: MNG-1076 > URL: http://jira.codehaus.org/browse/MNG-1076 > Project: Maven 2 > Type: Bug > Components: maven-eclipse-plugin > Versions: 2.0-beta-2 > Reporter: Juraj Burian > Assignee: John Casey > Priority: Minor > Attachments: maven-eclipse-plugin.patch, maven-eclipse-plugin.path, src.patch > > > Let: > <dependency> > <groupId>java</groupId> > <artifactId>tools</artifactId> > <version>1.5.03</version> > <systemPath>${java.home}/../lib/tools.jar</systemPath> > <scope>system</scope> > </dependency> > Generated classpathentry is: <classpathentry kind="var" path="M2_REPO/..."/> > By my opinion correct classpathentry looks like: <classpathentry kind="lib" > path="C:\Java\jdk1.5.0_03\lib\tools.jar"/> if <systemPath/> is absolute. > I have patch for you, see attached file. > best regards > J.Burian -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
