Hi, In "SVN", the release:perform step checks out the proposed "tag" and redoes the entire "build" using that. The artifacts that are deployed to the staging repo (repository.apache.org) are from that checkout.
(I think the "GitHub" version works the same way?) The artifacts that are are supposed to be the RC should also come from that checkout/build. I'm guessing that the RC files are incorrectly being taken from the wrong spot? If so, to correct this, please repost an RC2 without rerunning the build, but having the artifacts for the RC come from the "checkout" (release:perform) spot, instead. -Marshall On 1/15/2019 2:55 PM, Richard Eckart de Castilho wrote: > On 15. Jan 2019, at 20:33, Richard Eckart de Castilho <r...@apache.org> wrote: >> On 15. Jan 2019, at 14:57, Peter Klügl <peter.klu...@averbis.com> wrote: >>> Hmm yes, but it is empty in the downloadable zips, e.g., source-release >>> and bin. >> Hm... very odd. After the local build is complete, the file has the proper >> contents... >> But yes, you are right... in the distribution artifacts, it's simply empty... > This is very strange. > > The `uima-uimafit/issuesFixed/jira-report.html` file is empty (this is the > one included in the ZIPs. I guess this is created during the Maven > `release:prepare` step. > > But the `uima-uimafit/target/checkout/issuesFixed/jira-report.html` file > created during the Maven `release:perform` step only a few minutes later has > the correct contents. > > My best guess at this moment would be a temporary communication problem with > the Jira server. So if I just re-run the release, it might fix the problem... > > That would be a pretty annoying reason to cancel an RC and do a new one with > no changes at all... *sigh* > > -- Richard
