groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: Build failing
Date Wed, 21 Jun 2017 07:57:01 GMT
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 <paulk@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 <russel@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
>>
>>
>>
>

Mime
View raw message