[
https://issues.apache.org/jira/browse/BUILDR-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803179#action_12803179
]
Alex Boisvert commented on BUILDR-317:
--------------------------------------
Couple comments,
1) I'd like to make it an optional dependency, I'd suggest that "require
'java/ecj'" be required to use the ECJ compiler. That way, the ecj compiler
isn't downloaded by buildr if it's not used in the buildfile
2) We need specs for the updated :ecj compiler. (I think it's just a matter of
updating those for OSGiC that were attached previously)
3) I'd be inclined to make :ecj become the default compiler for Java projects
when require 'java/ecj' is present.
> ecj compiler
> ------------
>
> Key: BUILDR-317
> URL: https://issues.apache.org/jira/browse/BUILDR-317
> Project: Buildr
> Issue Type: New Feature
> Components: Compilers
> Affects Versions: 1.3.4
> Reporter: Antoine Toulme
> Assignee: Daniel Spiewak
> Attachments: buildr-317, compiler.rb, compiler_spec.rb
>
>
> The ECJ compiler is an advanced Java compiler that works on top of javac.
> It brings a lot of functionality built-in:
> -better error report (better indentation of the message)
> -better warnings (warnings for source code target VM for example, type
> casting)
> -more errors reported: the compiler doesn't stop after 100 errors, it will
> bring all the errors and warnings reported.
> The compiler passes all the javac specs. I added an attempt to check the
> output generated, but since it is made from Java, I can't control it as of
> now (see my post on the users mailing list for an idea on how to help with
> it).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
