[MECLIPSE-750] eclipse:eclipse generates classpathentry element to wrong JRE container

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.9
• Component/s: Core : Dependencies resolution and build path (.classpath)

Environment

Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T12:37:52-05:00)
Maven home: C:\Java\apache-maven-3.2.1\bin\..
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_45\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

• Assignee: Robert Scholte
• Reporter: Gary D. Gregory
• Created: 27/Mar/14 10:34
• Updated: 25/Dec/15 11:49
• Resolved: 25/Dec/15 11:49

Description

The eclipse:eclipse command does not use the parent POM to find compiler settings to generate the .classpath. Therefore, the file contains a classpathentry pointing to the default JRE.

To see this in action, check out revision 1582304 of Log4J2's trunk from https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk

From the root, run 'mvn eclipse:eclipse' then look in log4j-core/.classpath

The parent POM sets the compile source and target to 1.6. You can run this command with any version of Java, the default JRE will be set in the .classpath file, as opposed to:

<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>