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

["Robert Scholte (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MECLIPSE-235.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

The Apache Maven team has decided to retire the maven-eclipse-plugin, so this issue won't be fixed. 


> Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-235
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-235
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: New Feature
>          Components: Core : Dependencies resolution and build path (.classpath)
>         Environment: Should be OK for ALL
>            Reporter: Hasan Ceylan
>            Assignee: Robert Scholte
>         Attachments: eclipseM2Plugin.diff, q4t_patch.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)