nning into this
issue. I can now confirm that this now works fine with Jacoco 0.8.3 and
Java 13 (even the latest EA 8 build).
-Jaikiran
On 23/01/19 7:00 PM, Jaikiran Pai wrote:
Hi Dalibor,
On 23/01/19 2:51 PM, Dalibor Topic wrote:
On 23.01.2019 08:56, Jaikiran Pai wrote:
Our Ant testsuite against
n any newer
versions.
Hi Jaikiran,
the changes for experimental support of JDK 13 bytecode have just gone
into jacoco, per https://github.com/jacoco/jacoco/pull/835 .
cheers,
dalibor topic
--
Oracle <http://www.oracle.com>
Dalibor Topic | Principal Product Manager
Phone: +49408909121
l error message if javah is used but no longer
supported.
That sounds like a good plan.
When do you expect to know whether JEP 313 is going to make it into
Java10?
By Monday, December 4th, per
http://mail.openjdk.java.net/pipermail/jdk-dev/2017-November/000278.html .
cheers,
dalibor
On 01.08.2016 16:32, Stefan Bodewig wrote:
On 2016-08-01, dalibor topic wrote:
I'd also suggest a sideways glance at
https://bz.apache.org/bugzilla/show_bug.cgi?id=42838 again, in light
of the current minimal platform requirements for Ant.
Sure, unfortunately the ticket only has p
pletely unrelated: while adding support for javac's -h option
I realized the option wasn't mentioned inside javac's manual page at
all. Only javac -help talks about it.
Please see https://bugs.openjdk.java.net/browse/JDK-8065825 and related
issues.
cheers,
dalibor topi
show_bug.cgi?id=59909
I'm talking about build files with something like
which works fine on JDK<9 and will break (unless you set
java.locale.providers) on JDK9.
I suspect that https://bugs.openjdk.java.net/browse/JDK-8130845 may be
related.
cheers,
dalibor topic
[0] http:
On 27.07.2016 22:16, Stefan Bodewig wrote:
I will create a bug ticket for the datetime parsing problem once/if I
manage to create a stand-alone test case.
Thanks, Stefan!
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089
teFormat.parse(java.base@9-ea/DateFormat.java:366)
`
The same string is parsed without any problems on Java8 and earlier.
Does setting java.locale.providers as outlined at
https://wiki.openjdk.java.net/display/Adoption/JDK+9+Outreach#JDK9Outreach-UseCLDRLocaleDatabyDefault
help?
cheer
Thanks for stripping the test case down, Stefan - the behaviour sounds
rather odd.
Please file a bug at bugs.java.com, and let us know what issue ID you
receive.
cheers,
dalibor topic
On 29.05.2015 21:00, Stefan Bodewig wrote:
I've stripped down the test ca
that case, please let us know what the incident
id is.
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 | Mobile: +491737185961
Oracle | Kühnehöfe 5 | 22761 Hamburg
<http://www.oracle.com/commitment> Oracle is committ
longer supported. Use 1.6 or later.
error: Target option 1.1 is no longer supported. Use 1.6 or later.
Thanks, Stefan - I believe that issue is discussed in
https://bugs.openjdk.java.net/browse/JDK-8050105
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal P
y expected
to go away?
See https://bugs.openjdk.java.net/browse/JDK-8065702 &
https://bugs.openjdk.java.net/browse/JDK-8065675 for 8u40.
See http://openjdk.java.net/jeps/220 for JDK 9.
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +49
Stefan Bodewig apache.org> writes:
> Thank you for the clarification.
>
> Still, GNU JAXP is a nice alternative to try so we can be sure we
> don't write a Xerces-J only task.
Thanks!
cheers,
dalibor topic
it use them under the covers by passing a specific line to
configure, but by default it uses the 'pure java' implementation from GNU JAXP.
Both the libxmlj and GNU JAXP have now been merged into GNU Classpath, and will
14 matches
Mail list logo
