sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-8323) Use the JDK-provided JavaCompiler API instead of the Eclipse one
Date Wed, 20 Mar 2019 14:41:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797221#comment-16797221
] 

Robert Munteanu commented on SLING-8323:
----------------------------------------

That's a good point [~kwin]. I don't think we can unconditionally do this then. Maybe there
is a more complicated way where the {{commons.compiler}} bundle is based on the embedded compiler
and we add a new {{commons.compiler-eclipse}} bundle which contains the current ECJ implementation.

Anyway, that's more for the future, added it here so that it is not forgotten.

> Use the JDK-provided JavaCompiler API instead of the Eclipse one
> ----------------------------------------------------------------
>
>                 Key: SLING-8323
>                 URL: https://issues.apache.org/jira/browse/SLING-8323
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: Commons Compiler 2.3.8
>
>
> Using the Eclipse compiler API works fine, with two minor caveats:
> - the dependency must be upgraded periodically to get support for newer Java versions
> - we need to embed ecj (~2.7M)
> Since Java 7 the [JavaCompiler|https://docs.oracle.com/javase/7/docs/api/javax/tools/JavaCompiler.html]
API allows programmatic access to the system java compiler. We should instead try and use
this compiler.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message