Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337010 - Better detect java projects
Summary: Better detect java projects
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Fedorenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 338084 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-11 16:45 EST by Pascal Rapicault CLA
Modified: 2021-04-19 13:25 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2011-02-11 16:45:44 EST 
When a packaging type is unknown, we should give the user the opportunity to import it as a Java Project so the browsing of the code is still possible.
This should be proposed as part of the import workflow (still to be worked on) and also as a quick fix.

The quick fix should cause the addition of the lifecycle mapping metadata in the pom so this can be shared with others.
Comment 1 Igor Fedorenko CLA 2011-02-24 09:12:10 EST 
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.
Comment 2 Igor Fedorenko CLA 2011-02-24 09:12:59 EST 
*** Bug 338084 has been marked as a duplicate of this bug. ***
Comment 3 Igor Fedorenko CLA 2011-02-26 17:59:28 EST 
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
Comment 4 Paul Tatavu CLA 2011-03-01 14:07:24 EST 
Verified
Comment 5 Denis Roy CLA 2021-04-19 13:25:08 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/