8:04 a.m.
Hi all,
I've installed latest preview builds of:
- JDK 9 b28
- JDK 8u40 b04
Java 9 is new in our builds, so some considerations:
- The JVM option MaxPermSize, which was deprecated in Java8, is no
longer accepted and will fail bootstrap. Either you remove it from
your build path or enable -XX:+IgnoreUnrecognizedVMOptions
- asciidoctor-maven-plugin plugin fails: I'll disable it for now but
it would be great if someone could have a look at it, if it's a JVM
bug we should report it, and otherwise fixing the plugin would be
nice.
On Java 8, a warning:
I've not simply added this beta, but it replaces the current one we
had setup. I realize this is a rather aggressive move, but keep in
mind the current one wasn't a stable release but an early preview as
well.
I guess we might want to split this into a "JDK 8" and a "JDK
8-preview" ? But even our current JDK8 builds are still largely
failing, so I'd rather see some love on that first, then we can move
on into multiple builds.
I would love some help on:
- the animal-sniffer is still broken on Java 8, see what can be done
or let's discuss alternatives
- Some ORM tests are failing on Java8
- Define JDK 9 test builds for more projects:
http://ci.hibernate.org/view/JDK9/
Cheers,
Sanne
6:25 a.m.
On Sun 2014-09-07 14:04, Sanne Grinovero wrote:
- asciidoctor-maven-plugin plugin fails: I'll disable it for now
but
it would be great if someone could have a look at it, if it's a JVM
bug we should report it, and otherwise fixing the plugin would be
nice.
Can you point me to a URL showing the failure? I can try and contact the
relevant persons.
6:31 a.m.
On 8 September 2014 12:25, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
On Sun 2014-09-07 14:04, Sanne Grinovero wrote:
> - asciidoctor-maven-plugin plugin fails: I'll disable it for now but
> it would be great if someone could have a look at it, if it's a JVM
> bug we should report it, and otherwise fixing the plugin would be
> nice.
Can you point me to a URL showing the failure? I can try and contact the
relevant persons.
I did debug it, and found that Asciidoctor fails to initialize JRuby:
the JRuby engine checks which JVM it's being run on to generate
appropriate opcodes.. and refuses to start on JDK9.
I guess that's fair enough, so the question would be if there is an
easy way to disable the asciidoctor-maven-plugin from an environment
switch, or if we need to mess with Maven profiles.
6:57 a.m.
I've push the information to the Asciidoctor folks.
I don't know about any switch though. I guess we do have a way to enable
or disable doc generation but because of various preferences between
project leads, nothing is consistent.
On Mon 2014-09-08 12:31, Sanne Grinovero wrote:
On 8 September 2014 12:25, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
> On Sun 2014-09-07 14:04, Sanne Grinovero wrote:
>> - asciidoctor-maven-plugin plugin fails: I'll disable it for now but
>> it would be great if someone could have a look at it, if it's a JVM
>> bug we should report it, and otherwise fixing the plugin would be
>> nice.
>
> Can you point me to a URL showing the failure? I can try and contact the
> relevant persons.
I did debug it, and found that Asciidoctor fails to initialize JRuby:
the JRuby engine checks which JVM it's being run on to generate
appropriate opcodes.. and refuses to start on JDK9.
I guess that's fair enough, so the question would be if there is an
easy way to disable the asciidoctor-maven-plugin from an environment
switch, or if we need to mess with Maven profiles.
7:06 a.m.
Thanks!
I have no strong preference, just preferring to keep it on by default
as it generally runs quickly enough; but YMMV if it's slow for someone
and impairs quick experimentation I'd be fine to disable it.
But obviously we need a switch to turn it off for such cases as the
JDK not being compatible.
Sanne
On 8 September 2014 12:57, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
I've push the information to the Asciidoctor folks.
I don't know about any switch though. I guess we do have a way to enable
or disable doc generation but because of various preferences between
project leads, nothing is consistent.
On Mon 2014-09-08 12:31, Sanne Grinovero wrote:
> On 8 September 2014 12:25, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
> > On Sun 2014-09-07 14:04, Sanne Grinovero wrote:
> >> - asciidoctor-maven-plugin plugin fails: I'll disable it for now but
> >> it would be great if someone could have a look at it, if it's a JVM
> >> bug we should report it, and otherwise fixing the plugin would be
> >> nice.
> >
> > Can you point me to a URL showing the failure? I can try and contact the
> > relevant persons.
>
> I did debug it, and found that Asciidoctor fails to initialize JRuby:
> the JRuby engine checks which JVM it's being run on to generate
> appropriate opcodes.. and refuses to start on JDK9.
> I guess that's fair enough, so the question would be if there is an
> easy way to disable the asciidoctor-maven-plugin from an environment
> switch, or if we need to mess with Maven profiles.
9:15 a.m.
On Mon, Sep 08, 2014 at 01:06:16PM +0100, Sanne Grinovero wrote:
I have no strong preference, just preferring to keep it on by
default
as it generally runs quickly enough;
+1 for keeping things running per default (and it is a strong preference ;-))
But obviously we need a switch to turn it off for such cases as the
JDK not being compatible.
Do we right now? Can we not just wait a bit to things how things are shaping up?
I get the point of being pro-active, but do we need a Java 9 build right now?
I'll let the asciisoc and JRuby guys chew a little bit on this and see what
they come up with.
--Hardy
5:57 p.m.
On 8 September 2014 15:15, Hardy Ferentschik <hardy(a)hibernate.org> wrote:
On Mon, Sep 08, 2014 at 01:06:16PM +0100, Sanne Grinovero wrote:
> I have no strong preference, just preferring to keep it on by default
> as it generally runs quickly enough;
+1 for keeping things running per default (and it is a strong preference ;-))
> But obviously we need a switch to turn it off for such cases as the
> JDK not being compatible.
Do we right now? Can we not just wait a bit to things how things are shaping up?
I get the point of being pro-active, but do we need a Java 9 build right now?
I'll let the asciisoc and JRuby guys chew a little bit on this and see what
they come up with.
"Right now" can be flexible of course, but the JDK will come sooner
than usual. Having these tasks running doesn't necessarily imply that
our stuff will work fine but it means we'll have the knowledge to be
able to make informed decisions at lowest overhead (the earlier the
better).
I'd like us to be pro-active in terms of "our stuff will work on
Java9" but I don't want to spend cycles on debugging stuff on behalf
of asciidoc or JRuby to work on JDK9 too, so realistically we should
disable these and let other deal with it at their own pace.
Not least, we're engaged in a promise to the OpenJDK team to test
these builds, in exchange we get full attention to bug reports:
- https://wiki.openjdk.java.net/display/Adoption/Quality+Out+Reach
Sanne
6:13 a.m.
All,
I've updated the JDK versions on ci.hibernate.org to include
# Early Access build for JDK 9 b35 <https://jdk9.java.net/download/>
summary of changes: http://www.java.net/download/jdk9/changes/jdk9-b35.html
name on CI: Preview-JDK9
# Early Access build for JDK 8u40 b10 <http://jdk8.java.net/download.html>
summary of changes:
http://www.java.net/download/jdk8u40/changes/jdk8u40-b10.html
name on CI: Oracle JDK 8
But I still need your help to setup the project to actually use these
JDK's. I've setup Hibernate Search, I am hoping you could all take
ownership of one project you're most involved with and set it up as
well.
I still didn't disable asciidoctor on Hibernate Search, which fails
the documentation build, but besides that at least I know the tests
work fine.
Thanks,
Sanne
On 8 September 2014 23:57, Sanne Grinovero <sanne(a)hibernate.org> wrote:
On 8 September 2014 15:15, Hardy Ferentschik
<hardy(a)hibernate.org> wrote:
> On Mon, Sep 08, 2014 at 01:06:16PM +0100, Sanne Grinovero wrote:
>
>> I have no strong preference, just preferring to keep it on by default
>> as it generally runs quickly enough;
>
> +1 for keeping things running per default (and it is a strong preference ;-))
>
>> But obviously we need a switch to turn it off for such cases as the
>> JDK not being compatible.
>
> Do we right now? Can we not just wait a bit to things how things are shaping up?
> I get the point of being pro-active, but do we need a Java 9 build right now?
> I'll let the asciisoc and JRuby guys chew a little bit on this and see what
> they come up with.
"Right now" can be flexible of course, but the JDK will come sooner
than usual. Having these tasks running doesn't necessarily imply that
our stuff will work fine but it means we'll have the knowledge to be
able to make informed decisions at lowest overhead (the earlier the
better).
I'd like us to be pro-active in terms of "our stuff will work on
Java9" but I don't want to spend cycles on debugging stuff on behalf
of asciidoc or JRuby to work on JDK9 too, so realistically we should
disable these and let other deal with it at their own pace.
Not least, we're engaged in a promise to the OpenJDK team to test
these builds, in exchange we get full attention to bug reports:
- https://wiki.openjdk.java.net/display/Adoption/Quality+Out+Reach
Sanne
3684
days inactive
3728
days old
7 comments
3 participants
participants (3)
-
Emmanuel Bernard -
Hardy Ferentschik -
Sanne Grinovero