SNAPSHOT is up. Here is how I published it: 1008 ./dev-support/generate-hadoopX-poms.sh 0.96.0 0.96.0-hadoop1-SNAPSHOT 1009 ./dev-support/generate-hadoopX-poms.sh 0.96.0 0.96.0-hadoop2-SNAPSHOT 1011 export MAVEN=~/bin/mvn/bin/mvn 1012 ./dev-support/make_rc.sh
All is predicated on your settings.xml being set up properly referencing a key to sign the artifacts with. See the section in refguide on how to make release candidate for guidance. St.Ack On Fri, Sep 27, 2013 at 8:30 PM, Sergey Shelukhin <[email protected]>wrote: > Thanks! I got about halfway, at least now I have a pgp key :) > > > On Fri, Sep 27, 2013 at 5:00 PM, Stack <[email protected]> wrote: > > > On Fri, Sep 27, 2013 at 3:34 PM, Sergey Shelukhin < > [email protected] > > >wrote: > > > > > Thanks! Found the vote email urls. > > > Yeah, the motivation is the same, looking at some recent version of 96. > > So > > > someone should publish a snapshot manually again? > > > I can try to do it. > > > Can you quality "our shit is too big" wrt every-build publishing? Seems > > it > > > could be useful. > > > > > > > > We build many times a day and each tgz is 70-80MBs. We'd probably make > > someone upset -- it'd be my guess. Also might be awkward getting > > credentials into place up on jenkins to sign the deploy. > > > > Let me put up a snapshot for you. Takes a little time. Will flag you > when > > done. > > > > St.Ack > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
