Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350939 - Maven Dependencies classpath container does not show up
Summary: Maven Dependencies classpath container does not show up
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-01 09:57 EDT by Ulli Hafner CLA
Modified: 2021-04-19 13:23 EDT (History)
1 user (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 Ulli Hafner CLA 2011-07-01 09:57:03 EDT 
Build Identifier: I20110613-1736

In a fresh installation of Eclipse for Java Developers I tried to import the Jenkins maven projects (ssh://github.com/jenkinsci/jenkins.git). 

After the import, the modules jenkins-core and jenkins-test-harness do not have a classpath container for the Maven Dependencies showing up in the package explorer. Therefor, the Java files will not compile. 

In .classpath, the maven container is referenced:

<classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>


Reproducible: Always
Comment 1 Igor Fedorenko CLA 2011-07-01 10:57:52 EDT 
As far as I can tell, jenkins-core project uses non-standard java compiler and is not supported out-of-the-box by m2e. Please contact us on m2e-dev@eclipse.org list if you are interested to develop such support.
Comment 2 Ulli Hafner CLA 2011-07-06 08:12:00 EDT 
Hmm, this did work with all previous versions of m2e. And I don't think that Jenkins/Hudsons requires a different compiler than javac. I think this is a regression in m2e.
Comment 3 Igor Fedorenko CLA 2011-07-06 09:17:23 EDT 
Do "mvn help:effective-pom" and check if maven-compiler-plugin is bound to any build phase.
Comment 4 Igor Fedorenko CLA 2011-07-14 11:45:51 EDT 
I made some changes to AbstractJavaProjectConfigurator to allow customization of compiler plugin groupId, artifactId and goal names. It should be possible to develop m2e extension to support alternative (i.e. forked) maven-compiler-plugin implementations relatively easily now.


http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=c0e3be615997a389f62a64909b5ad3b252a393ca
Comment 5 Igor Fedorenko CLA 2011-08-01 03:29:43 EDT 
as far as I understand Jenkins does not use custom compiler plugin any more, so  more work is planned here.
Comment 6 Denis Roy CLA 2021-04-19 13:23:15 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/