I'm not aware of such a cli like tools (we have no maven project in this phase).
I populate RELEASE120 with inconsistent cluster pom dependencies. Only at build time of an application (for fun) involving 1 of the 2 bad constructed pom. So I had to go for RELEASE120-1. Best Regards Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : mardi 8 septembre 2020 18:28 À : dev <[email protected]> Objet : Re: Installer move and website update On Tue, 8 Sep 2020 at 14:50, Randall Wood <[email protected]> wrote: > The maven-enforcer-plugin can enforce a no snapshot rule prior to > uploading, but I don’t know of any ant toolkit that can enforce that Strictly speaking I'm not sure if it would - at least the version wasn't a snapshot in this case, it was in the artefact ID. Maybe other rules (ban dependencies?) could do this though? Ideally we'd be able to run all the checking that uploading and closing the staging repository does locally before attempting to upload. This doesn't have to involve Ant - the process already involves some local work and direct use of nexus-staging-maven-plugin - could run other Maven plugin actions directly (and in a CI check). 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 --------------------------------------------------------------------- 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
