You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/07/13 17:23:13 UTC

[jira] Commented: (MECLIPSE-235) Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.

    [ http://jira.codehaus.org/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102169 ] 

John Casey commented on MECLIPSE-235:
-------------------------------------

I added an eclipse:m2eclipse mojo in maven-eclipse-plugin 2.4-snapshot...will this suffice? It's not that well-tested, but I've been using it for over 6 months now without any problems...

> Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-235
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-235
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>         Environment: Should be OK for ALL
>            Reporter: Hasan Ceylan
>             Fix For: 2.5
>
>         Attachments: eclipseM2Plugin.diff
>
>
> When we create eclipse projects using the maven-eclipse-plugin, all the class path entries for the dependent libraries are added to the .classpath.
> For those like me who has eclipse maven plugin, enabling maven2 for the generated project creates duplicate libraries as maven also introduces its own container based on the information in the pom.xml.
> I took the liberty to modify the head, and introduced the "eclipse.withM2Plugin" parameter. If this parameter is true in the runtime,
> 1) In EclipsePlugin.setup()
> a) If "org.maven.ide.eclipse.maven2Nature" nature is not added in the configuration, it is added automatically.
> b) If "org.maven.ide.eclipse.maven2Builder" builder is not added in the configuration, it is added automatically.
> c) If "org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER" container is added automatically.
> 2) In config
> introduced the method hasMaven2Nature() which indicates if Maven2 nature is available
> 3) M2_REPO's skipped in EclipseClasspathWriter if config returns true for hasMaven2Nature()
> Hope you like the patch...
> Regards,
> Hasan Ceylan

-- 
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