The fix is not to use the internal APIs and rely on the "maven-publish"
plugin instead. Due to historical reasons, our publishing is a bit of a
mess, to say the least, so I was reluctant on changing it to avoid
breakages when publishing. One of the issues is that with our current
publishing strateg
Hi Andres,
That's great :-)
Cheers,
Daniel.Sun
-
Daniel Sun
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Hi Daniel,
Good (well not really but you understand what I mean ;-), I’ll have a peek at
the errors and see if a fix is possible in the next days.
Best
Andres
Sent from my primitive tricorder
> On Dec 11, 2018, at 18:10, Daniel.Sun wrote:
>
> Hi Cédric,
>
> How to fix the issue @_@
Hi Cédric,
How to fix the issue @_@
Cheers,
Daniel.Sun
-
Daniel Sun
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Hi Andres,
The build fails locally with the same error(path is different).
Cheers,
Daniel.Sun
-
Daniel Sun
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
It's not really surprising, the build has been using internal APIs for
years, I'm surprised it didn't break earlier :)
Le mar. 11 déc. 2018 à 17:08, Andres Almiray a écrit :
> Hi Daniel,
>
> Can the failure be reproduced locally or is it. TeamCity specific issue?
>
> Best
> Andres
>
> Sent from
Hi Daniel,
Can the failure be reproduced locally or is it. TeamCity specific issue?
Best
Andres
Sent from my primitive tricorder
> On Dec 11, 2018, at 17:04, Daniel.Sun wrote:
>
> Hi all,
>
> After upgrading gradle to 5.0, our build on teamcity has been
> failing... Here is the error me
