river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: svn error with http checkout (was: Re: about 3.0 artifacts and announcement)
Date Fri, 06 Jan 2017 15:32:10 GMT
I don't think commit should work on http, it should only be allowed on
https.

On Fri, Jan 6, 2017 at 2:36 PM, Zsolt Kúti <la.tinca@gmail.com> wrote:

> Just made a fresh http checkout (done with IDEA). It went fine, on commit
> it asked for special credentials.
>
> Zsolt
>
> On Fri, Jan 6, 2017 at 4:24 AM, Dan Rollo <danrollo@gmail.com> wrote:
>
> >  I was just trying to do a clean checkout from “trunk” to test the
> > build/release steps (and hopefully help with publishing binaries to
> > Central), but I’m getting a subversion error during checkout:
> >
> >
> > $ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk river
> > A    river/test
> > A    river/test/conf
> > ...
> > A    river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
> > A    river/test/quarantined-src/README
> > svn: E175002: GET request returned unexpected delta base:
> > /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
> >
> > Anybody else seeing similar issues with a clean checkout using “http”
> > (anonymous) url?
> >
> >
> > For kicks, I also tried the https URL given under the ‘Developer Access’
> > section (show below), and that worked.
> > Is this expected? If so, maybe we should change the 'Anonymous access’
> URL
> > docs to use https.
> >
> > $ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
> >
> >
> > -Dan
> >
> >
> >
> > From: Zsolt Kúti <la.tinca@gmail.com <mailto:la.tinca@gmail.com>>
> > Subject: about 3.0 artifacts and announcement
> > Date: January 5, 2017 at 3:51:07 PM EST
> > To: dev@river.apache.org <mailto:dev@river.apache.org>
> >
> >
> > Hi,
> >
> > Can somebody tell if our release process documentation is up-to date:
> > http://river.apache.org/dev-doc/building-a-release.html <
> > http://river.apache.org/dev-doc/building-a-release.html>
> >
> > As to the release, the last mail was:
> > http://mail-archives.apache.org/mod_mbox/river-dev/201610.
> > mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=
> > UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.
> > org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-
> > pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
> >
> > The 3.0.0 release artifacts (no binary) are available from here:
> > http://www.apache.org/dyn/closer.cgi/river/ <http://www.apache.org/dyn/
> > closer.cgi/river/>
> > So nothing is against a release announcement on our website, isn't  it?
> >
> >
> > If nobody else is willing to, I can take a look into how to add our jars
> to
> > maven repo,.
> >
> > Cheers,
> > Zsolt
>



-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org <http://zest.apache.org> - New Energy for Java

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