Hello Stian, > Am 05.06.2017 um 18:58 schrieb Stian Soiland-Reyes <st...@apache.org>: > > 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)
It’s a PITA to manually commit the archive to the distilled area. This should be automated as part of the release process. Regards, Benedikt > > > > On 28 May 2017 3:01 am, "Rob Tompkins" <chtom...@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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
