jdaugherty opened a new issue, #11:
URL: https://github.com/apache/grails-gradle-publish/issues/11

   ### Issue description
   
   The new Maven Central uses a `proxy` API to support the older Maven Central 
API.  This can be problematic if a release is published on accident and needs 
to be removed.  An error such as the following will occur when multiple 
deployments are present and the proxy API can't determine which one to use: 
   
                Execution failed for task ':findSonatypeStagingRepository'.
                > Too many repositories found for stagingProfileId: 
io.github.gpc, descriptionRegex: \b\Qgrails-cache-guava:7.0.0-RC1\E(\s|$). If 
some of the repositories are not needed, consider deleting them manually. Here 
are the repositories matching the regular expression: 
[ReadStagingRepository(repositoryId=io.github.gpc--11115578-f0b5-482c-954e-6449e7684be0,
 type=closed, transitioning=false, description=grails-cache-guava:7.0.0-RC1), 
ReadStagingRepository(repositoryId=io.github.gpc--5410e36a-485c-42c8-bdb4-c3c1e7a39fc6,
 type=closed, transitioning=false, description=grails-cache-guava:7.0.0-RC1), 
ReadStagingRepository(repositoryId=io.github.gpc--5976d70a-865a-4bc9-a033-37be6db66323,
 type=closed, transitioning=false, description=grails-cache-guava:7.0.0-RC1), 
ReadStagingRepository(repositoryId=io.github.gpc--95b3ba89-10b4-46f9-acfe-983d1be7ba2c,
 type=closed, transitioning=false, description=grails-cache-guava:7.0.0-RC1),
   
   
   When removing a deployment on Maven Central, the proxy API will not be aware 
of the removal.  This ticket is to either adopt the modern APIs or document 
this behavior.  See 
https://github.com/gradle-nexus/publish-plugin/issues/379#issuecomment-3029335956
 for how to recover if your deployment is in this state.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to