You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Gary Gregory (JIRA)" <ji...@codehaus.org> on 2014/03/27 16:35:59 UTC

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

Gary Gregory created MECLIPSE-750:
-------------------------------------

             Summary: eclipse:eclipse generates classpathentry element to wrong JRE container
                 Key: MECLIPSE-750
                 URL: https://jira.codehaus.org/browse/MECLIPSE-750
             Project: Maven Eclipse Plugin
          Issue Type: Bug
          Components: Core : Dependencies resolution and build path (.classpath)
    Affects Versions: 2.9
         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"
            Reporter: Gary Gregory


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



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)