Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 0.9.3
-
Fix Version/s: 0.9.4
-
Component/s: Project Configuration
-
Labels:None
-
Number of attachments :
Description
To provide out of the box compatibility with larger number of maven projects and improve overall experience when using default project configuration, we need to make the following changes to default m2e project configuration. See this dev-list thread for more information
- Remove support for separate output folders, all output goes to maven output folders
- never disable JDT scrubbing output folders
- run configurable maven goal(s) at the end of full eclipse build
- default goals are "process-test-classes" but can be configured via pom.xml
- resources always copied to outputfolder. filtering is on/off depending on pom.xml
- there is no optoin to disable filtering beyond standard maven configuration
- default goals are "process-resources resources:testResources" but can be configured via pom.xml
Issue Links
| This issue is duplicated by: | ||||
| MNGECLIPSE-378 | Update Source Folders adds resources folders as source folders, not as class folders |
|
|
|
| MNGECLIPSE-588 | Add global "use maven output folders" option |
|
|
|
| MNGECLIPSE-628 | Ability to specify output directory when importing project |
|
|
|
| MNGECLIPSE-617 | global preference to use maven output folder |
|
|
|
| This issue relates to: | ||||
| MNGECLIPSE-571 | Include support for executing plugins attached to the generated-sources lifecycle phase |
|
|
|
| This issue is depended upon by: | ||||
| MNGECLIPSE-380 | problem with workspace resolution of maven-plugin projects |
|
|
|
Implemented as described.