Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of gudnabrsam@gmail.com designates
 74.125.83.53 as permitted sender)
MIME-Version: 1.0
Reply-To: gudnabrsam@gmail.com
In-Reply-To: 
 <CAOGo0VZPxfyB7jdG+6Ow8vZB0rqz3wfsrV0zm7BHvD4zKJHwsg@mail.gmail.com>
References: 
 <CALznzY77cd+LBkA=tGBemHL83COmR0YPsVCg+eO+QWOU56fJWw@mail.gmail.com>
	<5256C912.6060606@apache.org>
	<CAE9L6G1Dy2=OWFb1nzUua7Q4sy6s5tt+-5yQDwmnuTuEf1QMLQ@mail.gmail.com>
	<CALznzY5VDn+SFXFkVL9-VCxGBntoduE5+5tL0OjxANhragN97w@mail.gmail.com>
	<CAE9L6G3PjkYh7QRnz0yaA_0Nuq+kL66yM-U8952079FDEe3Xpg@mail.gmail.com>
	<5257C38B.2030504@apache.org>
	<CAOGo0VZ35QRe5jdCaeBMiEfG6N-6sxBhcY=VMrADeXmLYdXQbA@mail.gmail.com>
	<D3D643BF-93FA-467C-B258-52093D42B5EE@dslextreme.com>
	<CAOGo0VY9dxO7ZcdQkqS-5zn34ZZRf9OWedyDRd+dgR=vN+OAsA@mail.gmail.com>
	<CAE9L6G1Q3SO=+vCwM_t2rFTLvWoy--OK1p5v2dfiyH-ayWz27w@mail.gmail.com>
	<CAOGo0VYOVr+ai-U77n2_p5hS=mvp=v85d7eeQnwVDsnoRO-Kng@mail.gmail.com>
	<CAE9L6G0s5ihDq=tYPkuqZHvAbpAeaD6q8bUh7igDb=7bnw8gvA@mail.gmail.com>
	<CAOGo0VZPxfyB7jdG+6Ow8vZB0rqz3wfsrV0zm7BHvD4zKJHwsg@mail.gmail.com>
Date: Tue, 15 Oct 2013 14:11:51 -0500
Message-ID: 
 <CAE9L6G1XLZ0TYzG2Rg-8-gv7Jk34D7AiFymvszqDMKjvW5RBdA@mail.gmail.com>
Subject: Re: [DISCUSS] Creating Project for Release Process Testing...
From: Matt Benson <gudnabrsam@gmail.com>
To: sebb <sebbaz@gmail.com>
Cc: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=001a11c28d3470556304e8cc5bec

--001a11c28d3470556304e8cc5bec
Content-Type: text/plain; charset=ISO-8859-1

>From the time I spent recently perusing their API docs, I would guess from
the fact that they qualify the URL scheme with a "1" version, that they
will preserve compatibility indefinitely.  If they alter their API I
presume it will use a different version ID on the URL.

Matt


On Tue, Oct 15, 2013 at 2:08 PM, sebb <sebbaz@gmail.com> wrote:

> On 15 October 2013 19:33, Matt Benson <gudnabrsam@gmail.com> wrote:
> > Asked on #asfinfra and got the link from bdemers: [1].  He says it will
> > change to [2] whenever Nexus is upgraded.
>
> Thanks!
>
> Just to clarify: is it just the link that will change, or will the API
> change as well?
>
> > Matt
> > [1]
> >
> https://repository.apache.org/nexus-core-documentation-plugin/core/docs/index.html
> > [2]
> >
> https://repository.apache.org/nexus-restlet1x-plugin/default/docs/index.html
> >
> >
> >
> > On Tue, Oct 15, 2013 at 12:23 PM, sebb <sebbaz@gmail.com> wrote:
> >>
> >> On 15 October 2013 17:54, Matt Benson <gudnabrsam@gmail.com> wrote:
> >> > We should probably investigate whether Nexus's REST APIs would be of
> any
> >> > use here; seemingly they would make it much more difficult to
> >> > inadvertently
> >> > delete the wrong file(s).
> >>
> >> I did try to find out about them.
> >> Unfortunately they are not documented anywhere public that I could
> >> find (and it appears they may not be stable).
> >> I did make some progress by recording the GUI, but that is obviously not
> >> ideal.
> >>
> >> > Matt
> >> >
> >> >
> >> > On Tue, Oct 15, 2013 at 11:33 AM, sebb <sebbaz@gmail.com> wrote:
> >> >
> >> >> On 14 October 2013 02:21, Ralph Goers <ralph.goers@dslextreme.com>
> >> >> wrote:
> >> >> >
> >> >> > On Oct 13, 2013, at 4:31 PM, sebb wrote:
> >> >> >
> >> >> >> Recently, I found that the Maven project RMs don't bother removing
> >> >> these.
> >> >> >> So the files are released to Maven Central with the rest.
> >> >> >> I assume that the Maven Central administrators don't care about
> the
> >> >> >> extra space needed.
> >> >> >>
> >> >> >> Now ASF source releases must be provided via the ASF mirror
> system.
> >> >> >> There does not seem to be any ruling on whether having additional
> >> >> >> copies of the source release elsehere is allowed or not.
> >> >> >>
> >> >> >> I tried asking on Infra whether source releases should only be
> >> >> >> published to the ASF mirror system, but got no answer.
> >> >> >> Perhaps someone else would like to try?
> >> >> >>
> >> >> >> It would obviously be a lot easier if the Nexus directory did not
> >> >> >> have
> >> >> >> to be purged of these files, as this has to be carefully
> >> >> >> co-ordinated
> >> >> >> with copying the files for the ASF mirror SVN repo.
> >> >> >
> >> >> > Whether they have to be removed or not as a user I find them being
> >> >> published to Maven central to be annoying since they are pretty much
> >> >> useless as Maven artifacts.
> >> >>
> >> >> Indeed.
> >> >>
> >> >> The issue here is that deleting files from a closed staging area is
> >> >> prone to errors as the Nexus GUI is quite fiddly (and the
> confirmation
> >> >> pop-up does not show the name of the file being deleted).
> >> >>
> >> >> >
> >> >> >>
> >> >> >>> I gave up trying to remove the absurd .asc.sha1 and
> >> >> >>> .asc.md5 files for JCI, there was too many of them (12 files per
> >> >> >>> artifact, 6 artifacts).
> >> >> >>
> >> >> >> That could be automated (I started working on a tool to do this,
> but
> >> >> >> other things intervened).
> >> >> >> It's a long-standing Maven bug. The files can be left, but it
> makes
> >> >> >> checking the directory tedious.
> >> >> >
> >> >> > See http://wiki.apache.org/logging/Log4j2ReleaseGuide step 11c.
>  I'm
> >> >> not sure why rm *.asc.md5 is a problem.  Even if they are in separate
> >> >> directories the find command works pretty well.
> >> >>
> >> >> Find and rm do not work on Nexus, which is one place where the
> >> >> spurious files are annoying.
> >> >> Also it's easy to delete the wrong file in Nexus (so this should be
> >> >> done before closing the staging area - if it is done at all)
> >> >>
> >> >> > Ralph
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> >> For additional commands, e-mail: dev-help@commons.apache.org
> >> >>
> >> >>
> >
> >
>

--001a11c28d3470556304e8cc5bec--