| Summary: | Better detect java projects | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Pascal Rapicault <pascal> |
| Component: | m2e | Assignee: | Igor Fedorenko <igor> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | julien.henry, vladt, youngm |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Pascal Rapicault
Underlying User Story. As a user, when I import a java project with custom packaging type (nexus-plugin, hpi, sonar-plugin, etc) I expect Eclipse workspace projects to have JDT nature, source folders and dependencies configured similarly to packaging=jar. Internally, we need to change how m2e detects java projects to rely on presence of maven-compiler-plugin with compilerId=javac (the default) in project execution plan. This should provide expected behaviour for vast majority of projects m2e is able to support without custom lifecycle mapping strategy implementation. *** Bug 338084 has been marked as a duplicate of this bug. *** Implemented. m2e enables java functionality based on presence maven-compiler-plugin with compilerId=javac. This default behaviour can be overridden for individual projects and for specific packaging types. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=83bba72a8c3e6702df1f642be342c73296444796 Verified |