[#MECLIPSE-227] mvn eclipse:eclipse for <packaging>pom</packaging> should create a .project file - jira.codehaus.org

Maven 2.x Eclipse Plugin

mvn eclipse:eclipse for <packaging>pom</packaging> should create a .project file

Created: 10/Feb/07 07:57 AM Updated: 08/Jun/07 04:56 PM Resolved: 08/Jun/07 04:56 PM

Return to search

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

all

Issue Links:

Duplicate

This issue duplicates:

~~MECLIPSE-223~~ Add dependencies to eclipse project build path when working on a pom project

~~MECLIPSE-216~~ Allow writing of .project files for pom projects if not workspace is specified

Description

« Hide

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.

Sort Order:

[ Permalink | « Hide ]

Max Bowsher added a comment - 16/Mar/07 01:48 PM

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.

[ Permalink | « Hide ]

Vincent Massol added a comment - 07/Jun/07 11:57 AM

I agree this feature is needed but the eclipse plugin should always generate Eclipse project files when the maven projects doesn't have children. This will avoid issues with Eclipse not supporting project hiearchies.