You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:31:42 UTC
[jira] (MECLIPSE-253) eclipse:eclipse should use classpath variable
JAVA_HOME or JDK_HOME when writing .classpath for tools.jar
[ https://jira.codehaus.org/browse/MECLIPSE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MECLIPSE-253.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> eclipse:eclipse should use classpath variable JAVA_HOME or JDK_HOME when writing .classpath for tools.jar
> ---------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-253
> URL: https://jira.codehaus.org/browse/MECLIPSE-253
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Environment: All.
> Reporter: Parag Mehta
>
> Classpath generated by eclipse:eclipse contains absolute reference to the jdk being used
> <classpathentry kind="lib" path="C:/app/Java/jdk1.5.0_11/lib/tools.jar"/>
> This creates a classpath that is not portable amongst multiple machines/developers (who may have the jdk installed elsewhere). Using variables like JAVA_HOME or JDK_HOME would yield a more portable result (like users are expected to define M2_REPO or the plugin can do so).
> <classpathentry kind="lib" path="JAVA_HOME/lib/tools.jar"/>
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)