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 2017/06/17 06:01:04 UTC
Build failing
I guess it is already known that the build fails with Gradle 4.0?
> Task :docGDK
Err: Error: Could not find or load main class org.codehaus.groovy.tools.DocGenerator
FAILURE: Build failed with an exception.
* Where:
Script '/home/users/russel/Repositories/Git/Forks/Groovy/gradle/docs.gradle' line: 138
* What went wrong:
Execution failed for task ':docGDK'.
> Java returned: 1
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED in 5m 33s
118 actionable tasks: 118 executed
Publishing build scan...
https://gradle.com/s/dbgpbsyhhzjyi
--
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: Build failing
Posted by Mario Garcia <ma...@gmail.com>.
+1 to what Russel said. Maybe given one example the rest can follow your
steps.
And course +1 to change whatever is necessary from your point of view.
El 17 jun. 2017 1:18 p. m., "Russel Winder" <ru...@winder.org.uk> escribió:
> On Sat, 2017-06-17 at 09:44 +0200, Cédric Champeau wrote:
> > Yes, there are apparently quite a few glitches after the upgrade.
>
> OK, it's not just me then. Which is good. Sort of.
>
> > Dear community, please give me the strength to rewrite this whole
> > build.
> > Need to make it cleaner, it accumulated too many years of hacking,
> > inherited from the Ant era. Time to do some cleanup!
>
> I think we have a Maven build after the Ant one and before the Gradle
> one. I know, I started it. :-)
>
> Also there was the modular rewrite, which put some hacks in along with
> the JDK version stuff.
>
> If you can put in place an overall new architecture for a Gradle 4.0
> build, and do an exemplar "module" then many of us can chip in doing
> the leg-work of all the other "modules". Also if there is a repository
> to clone and work in which is not the mainline, it can be cloned and
> builds tried.
>
> We are here to help, you are not alone.
>
> --
> 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: Build failing
Posted by Russel Winder <ru...@winder.org.uk>.
On Sat, 2017-06-17 at 09:44 +0200, Cédric Champeau wrote:
> Yes, there are apparently quite a few glitches after the upgrade.
OK, it's not just me then. Which is good. Sort of.
> Dear community, please give me the strength to rewrite this whole
> build.
> Need to make it cleaner, it accumulated too many years of hacking,
> inherited from the Ant era. Time to do some cleanup!
I think we have a Maven build after the Ant one and before the Gradle
one. I know, I started it. :-)
Also there was the modular rewrite, which put some hacks in along with
the JDK version stuff.
If you can put in place an overall new architecture for a Gradle 4.0
build, and do an exemplar "module" then many of us can chip in doing
the leg-work of all the other "modules". Also if there is a repository
to clone and work in which is not the mainline, it can be cloned and
builds tried.
We are here to help, you are not alone.
--
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: Build failing
Posted by Marcin Erdmann <ma...@proxerd.pl>.
I'm now trying to give you the strength to do so with the power of my mind
because I don't know any other way! ;)
Good luck, you'll need it.
On Sat, 17 Jun 2017 at 08:44, Cédric Champeau <ce...@gmail.com>
wrote:
> Yes, there are apparently quite a few glitches after the upgrade.
>
> Dear community, please give me the strength to rewrite this whole build.
> Need to make it cleaner, it accumulated too many years of hacking,
> inherited from the Ant era. Time to do some cleanup!
>
> 2017-06-17 8:01 GMT+02:00 Russel Winder <ru...@winder.org.uk>:
>
>> I guess it is already known that the build fails with Gradle 4.0?
>>
>>
>> > Task :docGDK
>> Err: Error: Could not find or load main class
>> org.codehaus.groovy.tools.DocGenerator
>>
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Script
>> '/home/users/russel/Repositories/Git/Forks/Groovy/gradle/docs.gradle' line:
>> 138
>>
>> * What went wrong:
>> Execution failed for task ':docGDK'.
>> > Java returned: 1
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output.
>>
>> BUILD FAILED in 5m 33s
>> 118 actionable tasks: 118 executed
>>
>> Publishing build scan...
>> https://gradle.com/s/dbgpbsyhhzjyi
>>
>>
>>
>>
>>
>> --
>> 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: Build failing
Posted by Paul King <pa...@asert.com.au>.
Forgot to mention, this is in the jacoco coverage reporting"
Execution failed for task ':jacocoAllReport'.
org.apache.tools.ant.BuildException: Error while creating report
On Wed, Jun 21, 2017 at 5:57 PM, Paul King <pa...@asert.com.au> wrote:
> Actually the quality build is still failing on the CI server (but not
> locally for me):
>
>
> *Caused by: java.lang.IllegalStateException: Can't add different class
> with same name: org/codehaus/groovy/runtime/DefaultGroovyMethods*
> That's quite possibly also Gradle 4 related. I'll take a deeper look when
> I get time but if anyone else is getting the error, please let me know.
>
> Cheers, Paul.
>
>
> On Sun, Jun 18, 2017 at 11:25 PM, Paul King <pa...@asert.com.au> wrote:
>
>> I agree that the build could do with lots of TLC but so far all of the
>> fixes seem to be due to the somewhat intrusive breaking change in Gradle 4
>> where different language class files (e.g. Groovy and Java) are placed in
>> different output directories.
>>
>> Although each required change was only small, I would have much preferred
>> a scheme whereby the existing behavior was maintained with nagware until
>> the build was tweaked at which point my build would benefit from the
>> presumed performance gains (or even something akin to the Java9 `--illegal-access`
>> kill switch to turn off the new behavior). But I guess that might not be
>> possible to do generally.
>>
>> Anyway, everything seems to be working again but we'll need to keep a
>> close eye on things. If anyone spots further warnings from Gradle 4, please
>> speak up.
>>
>> And just because it's working doesn't mean we shouldn't improve the
>> build! I am very much +1 for that.
>>
>> Cheers, Paul.
>>
>>
>> On Sat, Jun 17, 2017 at 5:44 PM, Cédric Champeau <
>> cedric.champeau@gmail.com> wrote:
>>
>>> Yes, there are apparently quite a few glitches after the upgrade.
>>>
>>> Dear community, please give me the strength to rewrite this whole build.
>>> Need to make it cleaner, it accumulated too many years of hacking,
>>> inherited from the Ant era. Time to do some cleanup!
>>>
>>> 2017-06-17 8:01 GMT+02:00 Russel Winder <ru...@winder.org.uk>:
>>>
>>>> I guess it is already known that the build fails with Gradle 4.0?
>>>>
>>>>
>>>> > Task :docGDK
>>>> Err: Error: Could not find or load main class
>>>> org.codehaus.groovy.tools.DocGenerator
>>>>
>>>>
>>>> FAILURE: Build failed with an exception.
>>>>
>>>> * Where:
>>>> Script '/home/users/russel/Repositories/Git/Forks/Groovy/gradle/docs.gradle'
>>>> line: 138
>>>>
>>>> * What went wrong:
>>>> Execution failed for task ':docGDK'.
>>>> > Java returned: 1
>>>>
>>>> * Try:
>>>> Run with --stacktrace option to get the stack trace. Run with --info or
>>>> --debug option to get more log output.
>>>>
>>>> BUILD FAILED in 5m 33s
>>>> 118 actionable tasks: 118 executed
>>>>
>>>> Publishing build scan...
>>>> https://gradle.com/s/dbgpbsyhhzjyi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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: Build failing
Posted by Paul King <pa...@asert.com.au>.
Actually the quality build is still failing on the CI server (but not
locally for me):
*Caused by: java.lang.IllegalStateException: Can't add different class with
same name: org/codehaus/groovy/runtime/DefaultGroovyMethods*
That's quite possibly also Gradle 4 related. I'll take a deeper look when I
get time but if anyone else is getting the error, please let me know.
Cheers, Paul.
On Sun, Jun 18, 2017 at 11:25 PM, Paul King <pa...@asert.com.au> wrote:
> I agree that the build could do with lots of TLC but so far all of the
> fixes seem to be due to the somewhat intrusive breaking change in Gradle 4
> where different language class files (e.g. Groovy and Java) are placed in
> different output directories.
>
> Although each required change was only small, I would have much preferred
> a scheme whereby the existing behavior was maintained with nagware until
> the build was tweaked at which point my build would benefit from the
> presumed performance gains (or even something akin to the Java9 `--illegal-access`
> kill switch to turn off the new behavior). But I guess that might not be
> possible to do generally.
>
> Anyway, everything seems to be working again but we'll need to keep a
> close eye on things. If anyone spots further warnings from Gradle 4, please
> speak up.
>
> And just because it's working doesn't mean we shouldn't improve the build!
> I am very much +1 for that.
>
> Cheers, Paul.
>
>
> On Sat, Jun 17, 2017 at 5:44 PM, Cédric Champeau <
> cedric.champeau@gmail.com> wrote:
>
>> Yes, there are apparently quite a few glitches after the upgrade.
>>
>> Dear community, please give me the strength to rewrite this whole build.
>> Need to make it cleaner, it accumulated too many years of hacking,
>> inherited from the Ant era. Time to do some cleanup!
>>
>> 2017-06-17 8:01 GMT+02:00 Russel Winder <ru...@winder.org.uk>:
>>
>>> I guess it is already known that the build fails with Gradle 4.0?
>>>
>>>
>>> > Task :docGDK
>>> Err: Error: Could not find or load main class
>>> org.codehaus.groovy.tools.DocGenerator
>>>
>>>
>>> FAILURE: Build failed with an exception.
>>>
>>> * Where:
>>> Script '/home/users/russel/Repositories/Git/Forks/Groovy/gradle/docs.gradle'
>>> line: 138
>>>
>>> * What went wrong:
>>> Execution failed for task ':docGDK'.
>>> > Java returned: 1
>>>
>>> * Try:
>>> Run with --stacktrace option to get the stack trace. Run with --info or
>>> --debug option to get more log output.
>>>
>>> BUILD FAILED in 5m 33s
>>> 118 actionable tasks: 118 executed
>>>
>>> Publishing build scan...
>>> https://gradle.com/s/dbgpbsyhhzjyi
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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: Build failing
Posted by Paul King <pa...@asert.com.au>.
I agree that the build could do with lots of TLC but so far all of the
fixes seem to be due to the somewhat intrusive breaking change in Gradle 4
where different language class files (e.g. Groovy and Java) are placed in
different output directories.
Although each required change was only small, I would have much preferred a
scheme whereby the existing behavior was maintained with nagware until the
build was tweaked at which point my build would benefit from the presumed
performance gains (or even something akin to the Java9 `--illegal-access`
kill switch to turn off the new behavior). But I guess that might not be
possible to do generally.
Anyway, everything seems to be working again but we'll need to keep a close
eye on things. If anyone spots further warnings from Gradle 4, please speak
up.
And just because it's working doesn't mean we shouldn't improve the build!
I am very much +1 for that.
Cheers, Paul.
On Sat, Jun 17, 2017 at 5:44 PM, Cédric Champeau <ce...@gmail.com>
wrote:
> Yes, there are apparently quite a few glitches after the upgrade.
>
> Dear community, please give me the strength to rewrite this whole build.
> Need to make it cleaner, it accumulated too many years of hacking,
> inherited from the Ant era. Time to do some cleanup!
>
> 2017-06-17 8:01 GMT+02:00 Russel Winder <ru...@winder.org.uk>:
>
>> I guess it is already known that the build fails with Gradle 4.0?
>>
>>
>> > Task :docGDK
>> Err: Error: Could not find or load main class
>> org.codehaus.groovy.tools.DocGenerator
>>
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Script '/home/users/russel/Repositories/Git/Forks/Groovy/gradle/docs.gradle'
>> line: 138
>>
>> * What went wrong:
>> Execution failed for task ':docGDK'.
>> > Java returned: 1
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output.
>>
>> BUILD FAILED in 5m 33s
>> 118 actionable tasks: 118 executed
>>
>> Publishing build scan...
>> https://gradle.com/s/dbgpbsyhhzjyi
>>
>>
>>
>>
>>
>> --
>> 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: Build failing
Posted by Cédric Champeau <ce...@gmail.com>.
Yes, there are apparently quite a few glitches after the upgrade.
Dear community, please give me the strength to rewrite this whole build.
Need to make it cleaner, it accumulated too many years of hacking,
inherited from the Ant era. Time to do some cleanup!
2017-06-17 8:01 GMT+02:00 Russel Winder <ru...@winder.org.uk>:
> I guess it is already known that the build fails with Gradle 4.0?
>
>
> > Task :docGDK
> Err: Error: Could not find or load main class org.codehaus.groovy.tools.
> DocGenerator
>
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/home/users/russel/Repositories/Git/Forks/Groovy/gradle/docs.gradle'
> line: 138
>
> * What went wrong:
> Execution failed for task ':docGDK'.
> > Java returned: 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED in 5m 33s
> 118 actionable tasks: 118 executed
>
> Publishing build scan...
> https://gradle.com/s/dbgpbsyhhzjyi
>
>
>
>
>
> --
> 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