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 <sun...@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 >
