Hi, if unless there is a strong reason for you to deploy this beta to Maven Central, I'd suggest to stop the process at the point where you would promote the staging repository. This is the last step which moves the release from the Sonatype Nexus to Maven Central. All automatic validation steps are done before that, when the repository is "closed".
To test the staged release, in some test project, you can add the staging repository to the POM of your test project. Most artifacts I have seen that use a "beta" qualified include a "-" after the beta: 2.1-beta-1 Cheers, -- Richard Am 03.03.2013 um 18:47 schrieb Daniel Naber <list2...@danielnaber.de>: > Hi, > > FYI, I'll now try to release 2.1-beta1. Not so much because we need a beta > release, but to become familiar with the Maven-based release process. We'll > see what happens... This may not even end up on languagetool.org, but only > on Maven Central (the server that keeps all Maven artifacts). > > Regards > Daniel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
