You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by Russel Winder <ru...@winder.org.uk> on 2016/09/24 09:43:45 UTC
Groovy build fail
I am getting:
:compileGroovy
Unrecognized option: -addmods
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
:compileGroovy FAILED
trying to build Groovy on JDK9. I thought we had been round this one
and fixed it.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Re: Groovy build fail
Posted by Russel Winder <ru...@winder.org.uk>.
It appears that the build is now working fine on JDK9 138. Well the
install and installGroovy tasks anyway. I guess I need to now try with
the distDoc task as well.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Re: Groovy build fail
Posted by Cédric Champeau <ce...@gmail.com>.
The change to setAccessible that Jochen is talking about is indeed a big
problem. It breaks Gradle too, in various ways. I'm not even sure we can
fix it while maintaining the same level of functionality.
2016-09-24 17:11 GMT+02:00 Russel Winder <ru...@winder.org.uk>:
> On Sat, 2016-09-24 at 14:38 +0200, Jochen Theodorou wrote:
> > On 24.09.2016 12:59, Russel Winder wrote:
> > [...]
> > >
> > > >
> > > > But to be sure... what JDK9 version are you using?
> > >
> > > The build hasn't worked for me for a while, but I was "elsewhere"
> > > in
> > > the FOSS-verse. 135 and now 137 both fail.
> >
> > try 134, should also get rid of the add-mods error
>
> I have to admit I'll stick to keeping the JDK9 up to date and waiting
> for Groovy to catch up. Given that JDK9 is on a weekly update, if
> Groovy is to say it is JDK9 compliant it needs to change as JDK9
> changes, even if the changes are really annoying. This is only going to
> become an issue for me when I get back to getting GPars in order for
> JDK8 and JDK9 in a few weeks time, so it is not a big deal just yet.
>
> --
> Russel.
> ============================================================
> =================
> Dr Russel Winder t: +44 20 7585 2200 voip:
> sip:russel.winder@ekiga.net
> 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
>
Re: Groovy build fail
Posted by Russel Winder <ru...@winder.org.uk>.
On Sat, 2016-09-24 at 14:38 +0200, Jochen Theodorou wrote:
> On 24.09.2016 12:59, Russel Winder wrote:
> [...]
> >
> > >
> > > But to be sure... what JDK9 version are you using?
> >
> > The build hasn't worked for me for a while, but I was "elsewhere"
> > in
> > the FOSS-verse. 135 and now 137 both fail.
>
> try 134, should also get rid of the add-mods error
I have to admit I'll stick to keeping the JDK9 up to date and waiting
for Groovy to catch up. Given that JDK9 is on a weekly update, if
Groovy is to say it is JDK9 compliant it needs to change as JDK9
changes, even if the changes are really annoying. This is only going to
become an issue for me when I get back to getting GPars in order for
JDK8 and JDK9 in a few weeks time, so it is not a big deal just yet.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Re: Groovy build fail
Posted by Jochen Theodorou <bl...@gmx.org>.
On 24.09.2016 12:59, Russel Winder wrote:
[...]
>> But to be sure... what JDK9 version are you using?
>
> The build hasn't worked for me for a while, but I was "elsewhere" in
> the FOSS-verse. 135 and now 137 both fail.
try 134, should also get rid of the add-mods error
bye Jochen
Re: Groovy build fail
Posted by Russel Winder <ru...@winder.org.uk>.
On Sat, 2016-09-24 at 12:05 +0200, Jochen Theodorou wrote:
[…]
>
> well, blame the jdk9 guys for deciding in the middle of things to
> suddenly follow the gnu style and make -addmods to --admods ;)
I can back blaming the JDK9 people. :-)
Java has been wrong about options and hyphens for years, I wonder why
they are changing? But now is the time to change, this is an alpha
software programme after all – even if I am using it as production.
> No seriously, I had one jigsaw build successfully building Groovy,
> just
> to have failures in the next one. JDK9 is still changing a lot. For
> example they decided to increase the level of encapsulation and
> exclude
> all non-public methods from the API you can use outside the module.
> With
> the consequence, that even setAccessible does not work for those
> anymore.
>
> But to be sure... what JDK9 version are you using?
The build hasn't worked for me for a while, but I was "elsewhere" in
the FOSS-verse. 135 and now 137 both fail.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Re: Groovy build fail
Posted by Jochen Theodorou <bl...@gmx.org>.
On 24.09.2016 11:43, Russel Winder wrote:
> I am getting:
>
> :compileGroovy
> Unrecognized option: -addmods
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> :compileGroovy FAILED
>
> trying to build Groovy on JDK9. I thought we had been round this one
> and fixed it.
well, blame the jdk9 guys for deciding in the middle of things to
suddenly follow the gnu style and make -addmods to --admods ;)
No seriously, I had one jigsaw build successfully building Groovy, just
to have failures in the next one. JDK9 is still changing a lot. For
example they decided to increase the level of encapsulation and exclude
all non-public methods from the API you can use outside the module. With
the consequence, that even setAccessible does not work for those anymore.
But to be sure... what JDK9 version are you using?
bye Jochen