[
https://issues.apache.org/jira/browse/BUILDR-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Toulme updated BUILDR-317:
----------------------------------
Attachment: buildr-317-with-specs
Here is the updated patch.
This patch comes with specs.
This patch makes the ecj compiler optional. People can require it by adding
explicitly: require 'buildr/java/ecj' at the top of their Buildfile.
This patch makes the ecj compiler the default one once required as tested in
the spec.
One big issue though. The spec doesn't run with the rest of the specs. It needs
to add the ecj compiler to the classpath before the Sandbox module is loaded.
By itself the spec runs but it won't work if you run rake spec. I can offer to
help more on this matter, but I guess for now committing the code and renaming
the file so that it doesn't end with spec is a good workaround.
> 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, buildr-317-with-specs, 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.
