I ran into this issue: https://issues.apache.org/jira/browse/GEODE-1215
Does this need to be fixed prior to release? Anthony > On Apr 11, 2016, at 10:52 PM, Anthony Baker <[email protected]> wrote: > > Filed as https://issues.apache.org/jira/browse/GEODE-1213. I’ve got a fix > out for review. > > Also note that the develop branch version is now set to 1.0.0-incubating.M3. > Please set the fix version accordingly when you resolve a JIRA ticket: > > - If you fix an issue on release/1.0.0-incubating.M2 set the fix version to > 1.0.0-incubating.M2 > - If you fix an issue on develop, set the fix version to 1.0.0-incubating.M3 > > Anthony > >> On Apr 11, 2016, at 3:00 PM, Anthony Baker <[email protected]> wrote: >> >> Seeing a build problem when signing jars: >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Execution failed for task ':extensions/geode-modules-assembly:signArchives'. >>> java.io.FileNotFoundException: >>> /Users/abaker/code/incubator-geode/extensions/geode-modules-assembly/build/libs/geode-modules-assembly-1.0.0-incubating.M2.jar >>> (No such file or directory) >> >> Perhaps the gradle build magic is insufficient to remove the signing task >> from this project. >> >> Anthony >> >>> On Apr 11, 2016, at 2:38 PM, Dan Smith <[email protected]> wrote: >>> >>> The release branch for M2 is release/1.0.0-incubating.M2. Check it out and >>> see if there are any issues we should fix before creating the release. >>> >>> I will create a release candidate on Wednesday and start a vote if there >>> are no outstanding issues with the release branch. >>> >>> Thanks! >>> -Dan >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
