Vladimir Sitnikov

I guess so. The thing is if publish and close need to be split into two different executions, then the "close" part should somehow get the staging repository id. I...

> which results in the error on closing which has to be examined using the Nexus UI I wonder if GNPP can figure out the result of the close operation...

Well, UI is sending a request to https://oss.sonatype.org/service/local/staging/repository/comgithubvavrcc-1003/activity I've tried to query `https://oss.sonatype.org/service/local/staging/repository/comgithubvavrcc-1003/activity` while the repository is being dropped, and the URL responds returns the full set of activities (including...

Here's a UI screenshot for the "missing javadoc" failure: I'm not sure if there are APIs to resolve `profile-target-matching-staging` into human-readable names. However, printing the messages for the rule failures...

The API to decode rule IDs to human-readable names is https://oss.sonatype.org/service/local/staging/rule_types It responds with ```json { "data":[ { "resourceURI":"https://oss.sonatype.org/service/local/staging/rule_types/no-release-allowed-staging", "id":"no-release-allowed-staging", "name":"No release action allowed", "description":"Rule that fails whenever a 'release'...

Just in case, there's https://oss.sonatype.org/service/local/staging/rule_sets which prints the required rule for the repositories, however, I don't think it is worth trying to parse and analyze it in the plugin. Here's...

Just in case, pgjdbc has the same IP: https://github.com/pgjdbc/pgjdbc/blob/08d81291c69d02d8973d6b39dac82bdaad91f2ee/pgjdbc/src/test/java/org/postgresql/test/jdbc2/ConnectTimeoutTest.java#L24-L25 Just in case, there's https://github.com/NetCrusherOrg/netcrusher-java that might help to inject the required failures

Ideally, the plugin should be able to infer the staging repository id based on the comment. In other words: if user wants to release `v3.0-rc5`, then the plugin should enumerate...

I just noticed https://github.com/gradle-nexus/publish-plugin/pull/36 added ability to configure repository description. So the missing bit is to add API to lookup the staging repository based on the description.

An automatic task to claim OSSRH groupId would be, well, wow.