Java compiler API not supporting non-standard options such as -XDignore.symbol.file?

[Peter Niederwieser]

Martin,

thanks for chiming in. I'm not quite sure how your remark relates to what I said. While it's true that it isn't currently possible to point Gradle's compiler API integration to an external JDK, this will be possible in the future. And it's easy to add because we can already run compilation in a separate JVM. But unlike when using the command-line compiler, the same JVM can potentially be used for many compilation jobs, which can speed up builds significantly.

Cheers,
Peter

On Oct 12, 2013, at 2:25 AM, Martin Buchholz <martinrb at google.com> wrote:

> 
> 
> 
> On Fri, Oct 11, 2013 at 5:12 PM, Peter Niederwieser <pniederw at gmail.com> wrote:
> David, Jon,
> 
> thanks for yours answers. It's not that *I* want or need to use internal JDK APIs, but that Gradle needs to support whatever the JDK command-line compiler supports. (We can't tell our users "when you switch from (say) Ant to Gradle, you need to refactor your codebase and can no longer use internal JDK classes". We've even had someone building the JSR-166 project with Gradle and running into this problem.) 
> 
> Hi Peter,
> 
> I help maintain the ant build infrastructure for the JSR-166 project.  We deliberately use various external javac's since different parts of the code base have different JDK targets.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20131012/1689e03a/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20131012/1689e03a/signature-0001.asc