The problem is that it seems to want to bump the next version to 1.14.0+1.0 instead of 1.15.0. Is this not something I should be concerned about?
-- Michael Mior [email protected] 2017-09-27 14:39 GMT-04:00 Julian Hyde <[email protected]>: > The log from release:prepare looks OK to me. (Yeah, maven makes a lot of > frightened noises.) > > I think you can go ahead, create an RC and start a vote. > > Julian > > > > On Sep 25, 2017, at 7:50 AM, Michael Mior <[email protected]> wrote: > > > > Actually, to delete the tag, it's `git push -f apache > > :refs/tags/branch-1.14` (since I want to keep the branch). That worked. I > > also did a force push to my release branch remove the commits created for > > the release so I can try again when the error is resolved. Here's the log > > from release:prepare in case that helps: > > https://gist.github.com/bede3799ec851987d4ea33c0aa7ae54c > > > > -- > > Michael Mior > > [email protected] > > > > 2017-09-24 23:46 GMT-04:00 Josh Elser <[email protected]>: > > > >> Woah, that's funky. I haven't seen that before. I'd have to inspect the > >> output of maven to understand what it (and the release-plugin) did. > >> > >> Maybe try a `mvn release:clean`, `git reset --hard` (as needed)? > >> > >> As long as the tag doesn't start with the characters "rel/", you should > be > >> able to remove it (with a `git push origin :$tagname`, e.g. `git push > >> origin :branch-1.14`). > >> > >> > >> On 9/24/17 11:21 PM, Michael Mior wrote: > >> > >>> This seems to have resolved the permissions issue. However, the version > >>> bump has produced 1.14+1.0 instead of 1.15. You can see this version in > >>> the > >>> Nexus repository > >>> > >>> https://repository.apache.org/service/local/repo_groups/publ > >>> ic/content/org/apache/calcite/calcite/1.14+1.0-SNAPSHOT/ > >>> calcite-1.14+1.0-20170925.030910-1.pom > >>> > >>> Any idea what may have gone wrong here and how to fix it? > >>> > >>> Also, due to a misunderstanding on my part, the tag pushed was > branch-1.14 > >>> instead of calcite-1.14.0. That I assume I can fix by just deleting the > >>> tag > >>> and then pushing a new tag. > >>> > >>> -- > >>> Michael Mior > >>> [email protected] > >>> > >>> 2017-09-22 22:41 GMT-04:00 Julian Hyde <[email protected]>: > >>> > >>> You need credentials to deploy to the maven repo. I think they go in > >>>> settings.xml. > >>>> > >>>> Something like this: > >>>> http://felix.apache.org/documentation/development/ > >>>> release-management-nexus.html > >>>> > >>>> Julian > >>>> > >>>> On Fri, Sep 22, 2017 at 5:33 PM, Michael Mior <[email protected]> > wrote: > >>>> > >>>>> I tried to deploy an RC for 1.14 this evening and I got the following > >>>>> message > >>>>> > >>>>> [INFO] [ERROR] Failed to execute goal > >>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy > >>>>> > >>>> (default-deploy) > >>>> > >>>>> on project calcite: Failed to deploy artifacts: Could not transfer > >>>>> artifact org.apache.calcite:calcite:pom:1.14 > >>>>> .0-20170923.003005-15 from/to apache.snapshots.https ( > >>>>> https://repository.apache.org/content/repositories/snapsho > >>>>> ts): Failed to transfer file: > >>>>> https://repository.apache.org/content/repositories/ > >>>>> > >>>> snapshots/org/apache/calcite/ca > >>>> > >>>>> lcite/1.14.0-SNAPSHOT/calcite-1.14.0-20170923.003005-15.pom. Return > >>>>> code > >>>>> is: 401, ReasonPhrase: Unauthorized. -> > >>>>> [Help 1] > >>>>> > >>>>> Help resolving would be appreciated. > >>>>> > >>>>> -- > >>>>> Michael Mior > >>>>> [email protected] > >>>>> > >>>> > >>>> > >>> > >
