releasing beta release
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 -- http://www.danielnaber.de -- 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
Re: releasing beta release
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
Re: releasing beta release
Am 03.03.2013 um 20:24 schrieb Daniel Naber list2...@danielnaber.de: On 03.03.2013, 18:52:48 Richard Eckart de Castilho wrote: 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. Okay, I will do that. How do you make a release without being asked for the password again and again? I already tried everything I could find on the web, including -Dgpg.passphrase=... -Darguments=-Dgpg.passphrase=... and setting a profile in my settings.xml. As we have 30 modules I don't want to re-enter the password that often. Very good question. I didn't investigate in detail but I noticed that I have some projects that keep on asking for passwords and others that do not. I think it's a matter of the version of the signing plugin being used. You could try running mvn versions:display-plugin-updates and add the latest version of the signing plugin to the pluginManagement section in your aggregator POM. You might also want to take the opportunity to (upgrade and) fix the versions of all other plugins involved in your build. Otherwise, setting up and running a gpg-agent might help, but I never tried that. Cheers, -- Richard -- 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
Re: releasing beta release
On 03.03.2013, 20:51:30 Richard Eckart de Castilho wrote: Otherwise, setting up and running a gpg-agent might help, but I never tried that. That's what worked in the end. The version is now at https://oss.sonatype.org/content/repositories/orglanguagetool-520/org/languagetool/, everybody feel free to test it. Actually I deleted the standalone module, because I think publishing that as a Maven artifact doesn't seem to make sense, does it? So this is mostly relevant to developers. Oh, I just see that languagetool-parent still references standalone (as a module, not as a dependency). Is that a problem? Regards Daniel -- http://www.danielnaber.de -- 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
Re: releasing beta release
Am 03.03.2013 um 23:06 schrieb Daniel Naber list2...@danielnaber.de: On 03.03.2013, 20:51:30 Richard Eckart de Castilho wrote: Otherwise, setting up and running a gpg-agent might help, but I never tried that. That's what worked in the end. The version is now at https://oss.sonatype.org/content/repositories/orglanguagetool-520/org/languagetool/, everybody feel free to test it. Actually I deleted the standalone module, because I think publishing that as a Maven artifact doesn't seem to make sense, does it? So this is mostly relevant to developers. Oh, I just see that languagetool-parent still references standalone (as a module, not as a dependency). Is that a problem? I cannot imagine why. Once the artifacts have been deployed, the module structure is no longer relevant. Cheers, -- Richard -- 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