Gradle 4.10.1 breaks modifyPom about gradle-nexus-plugin HOT 4 CLOSED

Hi Christian,

It's possible that an update of the Groovy library within Gradle led to a different behavior. It could possibly also be the result of a change to evaluation ordering. This plugin had to use afterEvaluate which is not great and can sometimes lead to undesirable behavior.

At the moment I don't have the time to debug the issue. It would be highly appreciated if you could dig into the issue and potentially send a PR. I also wanted to mention that the "old" Maven plugin used in the Nexus plugin has been deprecated more or less. Going forward, Gradle suggests to use the Maven Publish plugin. Optimally, the Nexus plugin would be ported to the Maven Publish plugin. Again, a contribution from the community would be highly appreciated.

from gradle-nexus-plugin.

It doesn't seem to work with gradle 4.6 either on my Android project. modifyPom is ignored

from gradle-nexus-plugin.

I just upgraded this plugin to use Gradle 4.10.2 and my tests that use modifyPom do not fail. Could you please provide a minimal, executable example that reproduces the issue as a GitHub repo (optimally without the use of the Android plugin)?

from gradle-nexus-plugin.

I am going to close this issue as I couldn't reproduce it. Please reopen if you are still facing a problem.

from gradle-nexus-plugin.