Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368233 - Lifecycle mapping for maven-compiler-plugin should support ecj (compilerId = eclipse)
Summary: Lifecycle mapping for maven-compiler-plugin should support ecj (compilerId = ...
Status: CLOSED DUPLICATE of bug 370983
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-10 06:31 EST by Anttix Mising name CLA
Modified: 2021-04-19 13:23 EDT (History)
3 users (show)

See Also:


Attachments
A minimal HelloWorld project tha demonstrates the problem (2.40 KB, application/x-zip-compressed)
2012-01-10 06:32 EST, Anttix Mising name CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anttix Mising name CLA 2012-01-10 06:31:02 EST
Build Identifier: 20110916-0149

If a Maven project is configured to use ecj compiler, the following errors appear when importing the project into eclipse:

- No marketplace entries found to handle maven-compiler-plugin:2.3.2:compile in Eclipse.  Please see Help for more information.
- No marketplace entries found to handle maven-compiler-plugin:2.3.2:testCompile in Eclipse.  Please see Help for more information.

A fix should be trivial.

http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.jdt/lifecycle-mapping-metadata.xml reads:
        <parameters>
          <compilerId>javac</compilerId>
        </parameters>

It should read:
        <parameters>
          <compilerId>javac</compilerId>
          <compilerId>eclipse</compilerId>
        </parameters>

Reproducible: Always

Steps to Reproduce:
1. Unpack example zip provided
2. Try to import it to Eclipse: File->Import->Maven->Existing Maven Projects
Comment 1 Anttix Mising name CLA 2012-01-10 06:32:08 EST
Created attachment 209253 [details]
A minimal HelloWorld project tha demonstrates the problem
Comment 2 Igor Fedorenko CLA 2012-01-10 06:35:31 EST
compilerId=eclipse support can be implemented by an external m2e extension.
Comment 3 Fred Bricon CLA 2012-03-15 05:13:47 EDT
You can install m2e-jdt-compiler (https://github.com/jbosstools/m2e-jdt-compiler) to fix this problem.

Related issue : #370983
Comment 4 M K CLA 2012-03-26 10:03:33 EDT
After switching to win7 few days ago I got the problem even for the standard compiler. 

*No marketplace entries found to handle Execution default-compile, in /pom.xml in Eclipse.  Please see Help for more information.

*No marketplace entries found to handle Execution default-testCompile, in /pom.xml in Eclipse.  Please see Help for more information.


My environment:
-Win 7
-eclipse 3.7.2 J2EE bundle
-m2e 1.0.200
-I used Hello World project attached by Anttix but removed the compiler specific part from pom.xml
Comment 5 M K CLA 2012-03-26 10:16:07 EDT
After some more resarch it seems that my problem was solved by updating maven installation to version 3.0.3/3.0.4.
Comment 6 Igor Fedorenko CLA 2012-05-21 09:42:07 EDT

*** This bug has been marked as a duplicate of bug 370983 ***
Comment 7 Denis Roy CLA 2021-04-19 13:23:01 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/