This is cool Anthony! Can you already push the signed artifacts there as well and call a vote ?
On Wed, Jan 13, 2016 at 11:33 AM, Anthony Baker <[email protected]> wrote: > Also, I uploaded the KEYS file and created the empty RC0 folder as Roman > suggested on another thread: > https://dist.apache.org/repos/dist/dev/incubator/geode/ > > Anthony > > > On Jan 13, 2016, at 10:20 AM, Anthony Baker <[email protected]> wrote: > > Ok, I’ve pushed a few changes onto the release/1.0.0-incubating.M1 branch: > > 1) KEYS file is present (GEODE-776) > 2) md5 / sha256 hashes are generated for distributions (GEODE-775) > 3) artifacts and distributions for release builds are signed (GEODE-775) > 4) generate sources / javadoc jars for maven publishing (GEODE-777) > 5) fix for building source from non-git directory (GEODE-778) > > To build on a release branch (where the version does not end with > -SNAPSHOT) you will need to set these properties in > ~/.gradle/gradle.properties: > > signing.keyId= > signing.password= > signing.secretKeyRingFile= > > One thing I noticed is that the publish target (`gradle publish`) only > uploads jars/poms for these projects: > > - gemfire-common > - gemfire-core > - gemfire-json > - gemfire-joptsimple > - gemfire-lucene > > and does not consider signature files, sources, or javadoc jars. GEODE-27 > discusses a related issue of fixing the dependencies / repositories listed > in the pom files. > > Anthony > > > -- William Markito Oliveira -- For questions about Apache Geode, please write to *[email protected] <[email protected]>*
