commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [all] Deploying components
Date Mon, 05 Jun 2017 21:40:12 GMT
I have used bin zips before to get to DLL files for example.

Gary

On Jun 5, 2017 9:58 AM, "Stian Soiland-Reyes" <stain@apache.org> wrote:

> Personally I am happy about source distributions accompanying the jars in
> Maven Central, which are actually rebuildable as opposed to the
> -source.jars.
>
> they continue to be retrievable using Maven version mechanisms, compares to
> more fragile scripts crawling archive.apache.org (dist only contains the
> latest version).
>
> The -bin archives are less useful, however I have used their hashes during
> RC testing to confirm the jars in staging reasonably match the RC in dist
> (this can also be achieved by simply unpacking the binary dist and
> navigating to the jars)
>
>
>
> On 28 May 2017 3:01 am, "Rob Tompkins" <chtompki@gmail.com> wrote:
>
> > Hello all,
> >
> > Benedikt and I were chatting last week about how the .tar and .zip
> > distributions get uploaded to nexus during "mvn deploy” and how annoying
> > that side effect of the deployment happens to be. Coincidentally, I just
> > ran across a note that  Mladen Turk added at the end of the
> commons-daemon
> > release guide:
> >
> > https://github.com/apache/commons-daemon/blob/trunk/
> > HOWTO-RELEASE.txt#L41-L43 <https://github.com/apache/
> > commons-daemon/blob/trunk/HOWTO-RELEASE.txt#L41-L43>
> >
> > I’m thinking: (1) interesting note, knowing that the problem still
> exists,
> > and (2) I wonder if there would be community appetite for an attempt at
> > adding better automation to the release process. I’m betting that with a
> > little effort we probably could improve the release experience at least a
> > little.
> >
> > Cheers,
> > -Rob
>

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