On Tue, 8 Sep 2020 at 13:24, Eric Barboni <[email protected]> wrote: > I would say it's better to close it and avoid merging on same staging repo. > But will this help the plugin ?
I'm not suggesting that, just closing it manually via the web UI. The plugin attempts to auto-close, times out, and then deletes the staging repository - seems to be doing roughly what is described at https://issues.sonatype.org/browse/NEXUS-10174 > For SNAPSHOT we may need detection at > 1) maven level by fixing nb-repository-plugin so we fail the build for > release (globally) . (On a normal maven release the release plugin to that > kind of check but what we do it's not standard) > 2) ant level by failing build in case of SNAPSHOT text detected in the maven > dependencies type of external. > > Option 2 sounds better because it fail earlier. Agreed on that, but I wondered if there was anyway to test the full repository against all the Apache rule set locally? Would pick up other potential problems before hitting repository.a.o with 800MB. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
