Thanks Greg, good work. Sent from my Samsung device. Include original message ---- Original message ---- From: Greg Trasuk <tras...@stratuscom.com> Sent: 13/01/2016 04:35:08 pm To: dev@river.apache.org Subject: deploy_river.groovy
OK, I updated both the 2.2 branch and trunk to include a slightly better-written ‘deploy_groovysh’ script, as in the commit message Now if you’d like to try building against the Maven artifacts locally, you can do ‘ant build.all’ from the main folder, then go into ‘poms’ and run ‘groovy deploy_river.sh -install’, which will install to your local Maven repository. If you leave off ‘-install’ the script will prompt you for your gpg passphrase and deploy to the Apache staging repository. With either option, you can add the ‘-dryrun’ option to see what commands will be executed, without actually running the commands. The script no longer has a version number in it. It wasn’t actually used, since the versions are in the pom files. So in future, we only need to rev the version numbers in the pom files. Cheers, Greg Trasuk > On Jan 12, 2016, at 9:17 AM, Dennis Reedy <dennis.re...@gmail.com> wrote: > > >> On Jan 12, 2016, at 745AM, Greg Trasuk <tras...@stratuscom.com> wrote >> >> Don’t look at me - I’ve never touched the one in ‘trunk’. In any case, I’ll >>take a look at it later today - Probably just copy the one over from 2.2 and >>change the version. > > Awesome, thanks Greg. > >
