ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Early Access builds of JDK 8u112 b03, JDK 9 b128 are available on
Date Wed, 27 Jul 2016 20:11:12 GMT
On 2016-07-26, dalibor topic wrote:

> On 25.07.2016 17:08, Stefan Bodewig wrote:

>> For <rmic> Ant was invoking sun.rmi.rmic.Main internally and this class
>> is no longer exported (and inside a module Ant wouldn't import
>> anyway). I'm a little bit worried that used in
>> <javac> and used in <javah> may
>> "disappear" in similar ways (or already have).

> Please see
> for the former and
> for the deprecation of the separate javah tool.

Good, this makes me feel better, at least a bit. It doesn't mean javah
will work as before (as its entry point may not get exported), but I
think I'll implement a froking javac, something like to get on the save
side and I've opened in order to support
javac -h.

>> [aside: removing native2ascii from the JDK as people could use ther
>> build tools which in turn use the JDK tool still strikes me as a curious
>> move]

> This is tracked at
> and was discussed on core-libs-dev at
> .

I know (Felix said so much in his bugzilla report), but I'm not sure how
many toolsmiths are subscribed there (I'm not).

> As far as I know, the native2ascii implementations in NetBeans or
> IntelliJ do not depend on the JDK tool.

I just looked through the build tools and found that sbt used Ant (and
thus was broken as well) and gradle doesn't provide built-in support for
native2ascii at all so people will be using Ant here as well.

Maven's native2ascii (the one I found, I don't know where the official
plugin went after codhauss closed the doors) is an independent
implementation but doesn't cover the -reverse case.

>> * rmic -Xnew doesn't work and fails with a strange error message. I know
>>   I've reported this before:

> Yes, this is

OK, I've opened
which should lead to fewer failing tests.

>> * some of the JAI tests fail, but I haven't had the time to really look
>>   into them, yet. JAI is not an area I felt confident in jumping in.

> JAI is not part of JDK 9 (or any other JDK release). It doesn't seem
> that it has seen much development in the past 10 or so years, judging
> by , fwiw.

It may be my environment, I vaguely recall seeing failures for OpenJDK
7/8 but not for the official Oracle java packages. It's unlikely I'm
going to spend much time trying to figure things out.

>> * Something has changed WRT date time parsing. Many of the <touch>
>>   invocations we use inside our tests fail (on my German locale system,
>>   in case this matters).

> Does setting java.locale.providers as outlined at
> help?

Not at first glance. Note that we explicitly specify the locale when
creating the DateFormat instance.

I'll try to extract a stand-alone test case and then open a bug.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message