Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
The eclipse plugin does not generate a build path with all the pom dependencies when applyed to a project which type is pom (while it performs ok when the project type is jar).
The maven book states that it is usefull to group acceptance tests of a J2EE application in a dedicated module which type is pom (See section 4.13 of the Mergere book "Better builds with maven"). Even if this project type is pom, the project contains unit test source files to be run as acceptance tests, so it is (more than) usefull to generate an eclipse project for developping those tests.
Unfortunately, at the time, you cannot generate an eclipse project with complete dependencies if the type of your maven project is pom.
Issue Links
| This issue duplicates: | ||||
| MECLIPSE-216 | Allow writing of .project files for pom projects if not workspace is specified |
|
|
|
| This issue is duplicated by: | ||||
| MECLIPSE-227 | mvn eclipse:eclipse for <packaging>pom</packaging> should create a .project file |
|
|
|