You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/05/15 17:30:01 UTC
[jira] [Resolved] (CASSANDRA-8241) Use ecj [was: javac] instead of
javassist
[ https://issues.apache.org/jira/browse/CASSANDRA-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Stupp resolved CASSANDRA-8241.
-------------------------------------
Resolution: Fixed
[test run|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-8241-udf-ecj-testall/3/| is blue
committed as 0282cd550ca119b7fab1d8c6d8ccc1054c316c03
> Use ecj [was: javac] instead of javassist
> -----------------------------------------
>
> Key: CASSANDRA-8241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8241
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Labels: udf
> Fix For: 2.2 rc1
>
> Attachments: 8241-ecj-v2.txt, 8241-ecj.txt, udf-java-javac.txt
>
>
> Using JDK's built-in Java-Compiler API has some advantages over javassist.
> Although compilation feels a bit slower, Java compiler API has some advantages:
> * boxing + unboxing works
> * generics work
> * compiler error messages are better (or at least known) and have line/column numbers
> The implementation does not use any temp files. Everything's in memory.
> Patch attached to this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)