hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: 0.96 version in apache maven repo
Date Fri, 27 Sep 2013 22:32:04 GMT
See the VOTE email.  Along w/ pointing out where the signed tgzs are, it
also lists a repo to use to get at the 'staged' RC up in maven (you'll need
to add the repo to your local settings.xml, the location for local
customization)

St.Ack


On Fri, Sep 27, 2013 at 3:24 PM, Sergey Shelukhin <sergey@hortonworks.com>wrote:

> Why isn't latest HBase build (96, or whatever) published anywhere (say as
> snapshot)?
> RCs would help but latest build would be even nicer.
>
>
> On Fri, Sep 27, 2013 at 3:04 PM, Elliott Clark <eclark@apache.org> wrote:
>
> > Currently the 0.96 branch's version isn't a snapshot.  So anything
> > that's published directly from the pristine source will have to be a
> > real release.
> >
> > Each of the RC's are put into a staging repo.  Would that help you
> > whenever we can get the next rc out ?
> >
> > On Fri, Sep 27, 2013 at 3:01 PM, Sergey Shelukhin
> > <sergey@hortonworks.com> wrote:
> > > Hi.
> > > Who manages the snapshots that are published to Apache repos?
> > > I am looking at
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/hbase/hbase-common/0.96.0-hadoop2-SNAPSHOT/
> > >  and I see that this has some version built on Sep 9.
> > >
> > > Is -SNAPSHOT version it supposed to be updated by regular build? Are
> RCs
> > > supposed to go there?
> > >
> > > Any objection to me publishing a recent build?
> > >
> > > --
> > > 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.
> >
>
> --
> 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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message