On Tue, Aug 18, 2009 at 11:16 PM, sebb<seb...@gmail.com> wrote: > On 16/08/2009, ant elder <antel...@apache.org> wrote: >> On Sat, Aug 15, 2009 at 9:59 AM, sebb<seb...@gmail.com> wrote: >> > On 15/08/2009, ant elder <ant.el...@gmail.com> wrote: >> >> On Wed, Aug 12, 2009 at 7:13 PM, sebb AT ASF<s...@apache.org> wrote: >> >> > Please review and vote on the BSF 3.0 RC1 release. >> >> > The artifacts are available at: >> >> > >> >> > http://people.apache.org/~sebb/bsf-3.0-RC1/ >> >> > >> >> > and the an SVN tag is at: >> >> > >> >> > http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.0-rc1/ >> >> > >> >> > The vote will be open for at least 72 hours. >> >> > >> >> > S/// >> >> > >> >> >> >> > --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: bsf-dev-unsubscr...@jakarta.apache.org >> >> > For additional commands, e-mail: bsf-dev-h...@jakarta.apache.org >> >> > >> >> > >> >> >> >> >> >> Whats there looks good, +1 >> >> >> >> There's no Maven staging repo, could that be added to this vote? >> >> >> > >> > Sorry, I've no idea how to do that. >> > >> >> >> We really need to set up the BSF pom.xml so it can be done >> automatically with a build profile but it can be done manually with a >> bit of fiddling and the two commands below. I've done this now from a >> checkout of the 3.0 RC1 tag so we could just use those artifacts which >> i've put at: >> >> http://people.apache.org/~antelder/bsf/3.0-rc1/maven/ >> >> ...ant >> >> mvn >> -DaltDeploymentRepository=apache.rsync::default::scp://people.apache.org/home/antelder/public_html/bsf/3.0-rc1/maven >> verify gpg:sign install:install deploy:deploy >> >> >> mvn gpg:sign-and-deploy-file -DgroupId=org.apache.bsf >> -DartifactId=bsf-all -Dversion=3.0 -Dpackaging=jar >> -Dfile=bsf-all-3.0.jar -DrepositoryId=apache.rsync >> -Durl=scp://people.apache.org/home/antelder/public_html/bsf/3.0-RC1/maven >> > > Thanks. > > I take it that the first command deploys all but bsf-all, and the > second one deploys bsf-all? > > There seems to be a problem with the bsf-all pom.xml file - the AL > header is missing. >
Its a generated pom.xml file that Maven creates during the deploy-file command. It is possible to point the deploy-file to use an existing pom.xml so if you think its an issue we could take that generated pom.xml, add the AL header, and redo the deploy-file telling it to use the updated file. ...ant --------------------------------------------------------------------- To unsubscribe, e-mail: bsf-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: bsf-dev-h...@jakarta.apache.org
