You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2006/07/05 16:16:22 UTC

[jira] Closed: (MNGECLIPSE-152) Duplicate libraries when enabling maven

     [ http://jira.codehaus.org/browse/MNGECLIPSE-152?page=all ]
     
Eugene Kuleshov closed MNGECLIPSE-152:
--------------------------------------

    Resolution: Won't Fix

The whole point of this plugin is to avoid dealing with static generated projects.

> Duplicate libraries when enabling maven
> ---------------------------------------
>
>          Key: MNGECLIPSE-152
>          URL: http://jira.codehaus.org/browse/MNGECLIPSE-152
>      Project: Maven 2.x Extension for Eclipse
>         Type: Bug

>  Environment: eclipse 3.1.0 (windows)
>     Reporter: Stefan
>     Assignee: Eugene Kuleshov
>     Priority: Trivial

>
>
> Maven has a guideline for creating eclipse projects:
> http://maven.apache.org/guides/mini/guide-ide-eclipse.html
> When following these guidelines you'll end up with one java project for each module.
> When the maven plugin is enabled for these projects, eclipse will start to complain about duplicate libraries.
> One reference is generated by the maven command from the guideline, the other by the plugin.
> Although easy to solve, it would be nice if the plugin would recognize the maven generated projects and handle them correctly.

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