Thanks, I got some clarity from reviewing https://github.com/apache/samza/blob/master/RELEASE.md <https://github.com/apache/samza/blob/master/RELEASE.md>.
Given the problems [1] that gradle maven-publish has with signature files (and signing poms) I think we’ll need to rework some build files. Anthony [1] https://issues.gradle.org/browse/GRADLE-3183 <https://issues.gradle.org/browse/GRADLE-3183> > On Jan 13, 2016, at 5:21 PM, Roman Shaposhnik <[email protected]> wrote: > > On Wed, Jan 13, 2016 at 10:23 AM, Anthony Baker <[email protected]> wrote: >> Doesn’t uploading artifacts to Maven require credentials? >> I assume that issuing a `gradle publish` command will fail. What is the >> recommended approach? > > Just follow the document I sent out and try it. There's no danger in trying > it -- you can undo the transaction from the ASF Maven Nexus UI. Try it > and let us know. > > Thanks, > Roman.
signature.asc
Description: Message signed with OpenPGP using GPGMail
