You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by "Daniel.Sun" <su...@apache.org> on 2018/12/11 16:04:27 UTC

About downgrading gradle to 4.10.3 on master

Hi all,

      After upgrading gradle to 5.0, our build on teamcity has been
failing... Here is the error message:

org.gradle.api.InvalidUserDataException: File
'/var/teamcity/buildagent-jdk8/work/cba52975ead8186f/target/poms/pom-groovy.xml'
specified for property 'mavenDescriptor' does not exist. [1]

      As a result, groovy snapshots fails to publish to
https://oss.jfrog.org/oss-snapshot-local/ , and impacts some impatient users
who eagerly want to use the latest version of groovy 3.0.

      To be honest, I'm not a gradle expert and failed to fix the build
issue, so I propose to downgrade gradle to 4.10.3 for the time being if the
build issue has not been fixed for a long time.

      BTW, if gradle expert Cedric could set aside some spare time to look
into the build issue, that would be great :-)

Cheers,
Daniel.Sun

[1]
http://ci.groovy-lang.org/viewLog.html?buildId=53717&tab=buildResultsDiv&buildTypeId=Groovy_Jdk8Build_PlusSnapshotDeploy&guest=1 





-----
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

Re: About downgrading gradle to 4.10.3 on master

Posted by "Daniel.Sun" <su...@apache.org>.
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

Re: About downgrading gradle to 4.10.3 on master

Posted by Cédric Champeau <ce...@gmail.com>.
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 strategy it's hard to get the generated POMs to compare with the
new strategy and make sure we miss nothing.

Le mar. 11 déc. 2018 à 18:47, Daniel.Sun <su...@apache.org> a écrit :

> 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
>

Re: About downgrading gradle to 4.10.3 on master

Posted by "Daniel.Sun" <su...@apache.org>.
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

Re: About downgrading gradle to 4.10.3 on master

Posted by Andres Almiray <aa...@gmail.com>.
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 <su...@apache.org> wrote:
> 
> 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

Re: About downgrading gradle to 4.10.3 on master

Posted by "Daniel.Sun" <su...@apache.org>.
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

Re: About downgrading gradle to 4.10.3 on master

Posted by Cédric Champeau <ce...@gmail.com>.
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 <aa...@gmail.com> a écrit :

> 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 <su...@apache.org> wrote:
> >
> > Hi all,
> >
> >      After upgrading gradle to 5.0, our build on teamcity has been
> > failing... Here is the error message:
> >
> > org.gradle.api.InvalidUserDataException: File
> >
> '/var/teamcity/buildagent-jdk8/work/cba52975ead8186f/target/poms/pom-groovy.xml'
> > specified for property 'mavenDescriptor' does not exist. [1]
> >
> >      As a result, groovy snapshots fails to publish to
> > https://oss.jfrog.org/oss-snapshot-local/ , and impacts some impatient
> users
> > who eagerly want to use the latest version of groovy 3.0.
> >
> >      To be honest, I'm not a gradle expert and failed to fix the build
> > issue, so I propose to downgrade gradle to 4.10.3 for the time being if
> the
> > build issue has not been fixed for a long time.
> >
> >      BTW, if gradle expert Cedric could set aside some spare time to look
> > into the build issue, that would be great :-)
> >
> > Cheers,
> > Daniel.Sun
> >
> > [1]
> >
> http://ci.groovy-lang.org/viewLog.html?buildId=53717&tab=buildResultsDiv&buildTypeId=Groovy_Jdk8Build_PlusSnapshotDeploy&guest=1
> >
> >
> >
> >
> >
> > -----
> > 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
>

Re: About downgrading gradle to 4.10.3 on master

Posted by Andres Almiray <aa...@gmail.com>.
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 <su...@apache.org> wrote:
> 
> Hi all,
> 
>      After upgrading gradle to 5.0, our build on teamcity has been
> failing... Here is the error message:
> 
> org.gradle.api.InvalidUserDataException: File
> '/var/teamcity/buildagent-jdk8/work/cba52975ead8186f/target/poms/pom-groovy.xml'
> specified for property 'mavenDescriptor' does not exist. [1]
> 
>      As a result, groovy snapshots fails to publish to
> https://oss.jfrog.org/oss-snapshot-local/ , and impacts some impatient users
> who eagerly want to use the latest version of groovy 3.0.
> 
>      To be honest, I'm not a gradle expert and failed to fix the build
> issue, so I propose to downgrade gradle to 4.10.3 for the time being if the
> build issue has not been fixed for a long time.
> 
>      BTW, if gradle expert Cedric could set aside some spare time to look
> into the build issue, that would be great :-)
> 
> Cheers,
> Daniel.Sun
> 
> [1]
> http://ci.groovy-lang.org/viewLog.html?buildId=53717&tab=buildResultsDiv&buildTypeId=Groovy_Jdk8Build_PlusSnapshotDeploy&guest=1 
> 
> 
> 
> 
> 
> -----
> 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