maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <j...@codehaus.org>
Subject [jira] (MCOMPILER-144) Using compiler API instead of tools.jar
Date Wed, 02 Apr 2014 15:13:00 GMT

     [ https://jira.codehaus.org/browse/MCOMPILER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anders Hammar closed MCOMPILER-144.
-----------------------------------

    Resolution: Fixed

> Using compiler API instead of tools.jar
> ---------------------------------------
>
>                 Key: MCOMPILER-144
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-144
>             Project: Maven Compiler Plugin
>          Issue Type: New Feature
>            Reporter: Markus KARG
>            Priority: Minor
>
> Currently (MVN 3.0) java compilation needs tools.jar provided by the Sun JDK:
> [ERROR] Unable to locate the Javac Compiler in:
> [ERROR] C:\Program Files\Java\jre6\..\lib\tools.jar
> [ERROR] Please ensure you are using JDK 1.4 or above and
> [ERROR] not a JRE (the com.sun.tools.javac.Main class is required).
> [ERROR] In most cases you can change the location of your Java
> [ERROR] installation by setting the JAVA_HOME environment variable.
> In fact, this is bad because (a) it assumes that a full JDK is installed just for this
sole tool where a JRE would be sufficient, (b) tools.jar is not contained in any standards
documents and such possibly is not existing on future or non-sun JDK.
> Since JRE 6 (i. e. for many years) the JRE (not JDK!) comes with a standardized (!) API
for compilation: The Java Compiler API. It would make sense to use that standardized API instead
of forcing the user to have Sun JDK installed.



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

Mime
View raw message