Not clear to me how this happened. I was posting artifacts to the Apache staging area: URL: *https://dist.apache.org/repos/dist/dev/uima/eclipse-update-site/uima-as <https://dist.apache.org/repos/dist/dev/uima/eclipse-update-site/uima-as>*
I followed the same steps to release 2.9.0 as I did for 2.8.1. Somehow I must have been distracted to deviate from my release script and did something stupid apparently but I wish I remembered how I did that. For 2.9.0 RC2 I will follow the same script and check at each step if I can reproduce the problem. In any case, I used svn magic to revert artifacts back to 2.8.1 level using: svn merge -c -11721 <artifact name> -jerry On Mon, Dec 5, 2016 at 11:31 AM, Marshall Schor (JIRA) <[email protected]> wrote: > Marshall Schor created UIMA-5200: > ------------------------------------ > > Summary: leak of some meta artifacts prior to release to > uima-as eclipse-update site > Key: UIMA-5200 > URL: https://issues.apache.org/jira/browse/UIMA-5200 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout, Build, Packaging and Test, Eclipse > plugins > Affects Versions: 2.9.0AS > Reporter: Marshall Schor > Assignee: Jerry Cwiklik > Fix For: 2.9.0AS > > > It appears that the uima-as RC1 leaked some metadata artifacts for the > Eclipse update site to the official release. (the content and artifact jars > and their signatures, look at the dates on the files here: > http://www.apache.org/dist/uima/eclipse-update-site/uima-as/ > > These should be reverted, and the release process fixed to not update this > site until the release is approved. > > Note that the plugins themselves were not copied to the release site. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
