You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jim Mochel (JIRA)" <ji...@codehaus.org> on 2005/05/17 02:22:34 UTC
[jira] Created: (MNG-409) eclipse:eclipse creates overlapping projects
eclipse:eclipse creates overlapping projects
--------------------------------------------
Key: MNG-409
URL: http://jira.codehaus.org/browse/MNG-409
Project: m2
Type: Bug
Versions: 2.0-alpha-2
Environment: Linux and Windows 2000, Eclipse 3.1 m7
Reporter: Jim Mochel
Priority: Minor
Having hand generated an m2 project (with several modules) I ran the goal eclipse:eclipse against the root project. It worked on the projects for the modules but it also created a .project and .classpath for the root level. Those .project and .classpath files are unusable as is and prevent the user from pointing the eclipse import command at the root directory and having the import bring in all the projects.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Resolved: (MNG-409) eclipse:eclipse creates overlapping projects
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-409?page=all ]
Kenney Westerhof resolved MNG-409:
----------------------------------
Resolution: Won't Fix
This is an eclipse problem, not an m2 problem. Eclipse can't handle nested projects.
You can however have a root pom, but it needs <packaging>pom</packaging>. Always make sure
the projects NOT having pom packaging are leafs of the project tree.
There is currently an alternative: specify -Declipse.workspace=path/to/workspace.
The plugin will create a directory for each project there containing .classpath and .project files,
and create eclipse Links to the pom and source/resource directories. This way even nested projects
with non-pom packaging can be imported.
> eclipse:eclipse creates overlapping projects
> --------------------------------------------
>
> Key: MNG-409
> URL: http://jira.codehaus.org/browse/MNG-409
> Project: Maven 2
> Type: Bug
> Versions: 2.0-alpha-2
> Environment: Linux and Windows 2000, Eclipse 3.1 m7
> Reporter: Jim Mochel
> Priority: Minor
>
>
> Having hand generated an m2 project (with several modules) I ran the goal eclipse:eclipse against the root project. It worked on the projects for the modules but it also created a .project and .classpath for the root level. Those .project and .classpath files are unusable as is and prevent the user from pointing the eclipse import command at the root directory and having the import bring in all the projects.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org