Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:all
-
Number of attachments :
Description
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.
Issue Links
| This issue duplicates: | ||||
| MECLIPSE-216 | Allow writing of .project files for pom projects if not workspace is specified |
|
|
|
| MECLIPSE-223 | Add dependencies to eclipse project build path when working on a pom project |
|
|
|
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.