You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Max Bowsher (JIRA)" <ji...@codehaus.org> on 2007/03/16 19:48:34 UTC
[jira] Commented: (MECLIPSE-227) mvn eclipse:eclipse for
pom should create a .project file
[ http://jira.codehaus.org/browse/MECLIPSE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90276 ]
Max Bowsher commented on MECLIPSE-227:
--------------------------------------
Personally, I find the fact that it does not create a .project file to be an advantage. It means that I can easily import a multiproject tree into Eclipse just by pointing it at the root directory and letting it discover all the .project files. If there was a .project in the packaging=pom directories, it would not recurse into them.
> mvn eclipse:eclipse for <packaging>pom</packaging> should create a .project file
> --------------------------------------------------------------------------------
>
> Key: MECLIPSE-227
> URL: http://jira.codehaus.org/browse/MECLIPSE-227
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Environment: all
> Reporter: THURNER rupert
>
> mvn eclipse:eclipse for <packaging>pom</packaging> should create a .project file.
> currently it does nothing. this is especially annoying if using parent poms with other poms in subdirectories, see also description on http://maven.apache.org/guides/mini/guide-ide-eclipse.html.
--
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