If no other issues show up, I'm thinking this isn't significant enough to redo this release candidate. The Jira report plugin I think can be configured to just search out issues that are "fixed" in some version, without filtering on the "component".
In my checking: install into eclipse 4.3.2 -OK. I made Ruta project, switch to ruta perspective -ok. Signatures OK. (I did notice the signature is still not in the Apache ring of trust...) Build from source - OK. I note that non-official maven repos (zoidberg.ukp.informatik.tu-darmstadt.de) are still being depended upon. Is there any thought about finding a better (more secure) solution for this? License check in the Eclispe Jars - I checked a bunch of these - they look all OK. As does the source-release. [X] +1 OK to release -Marshall On 9/6/2014 5:59 PM, Peter Klügl wrote: > ... must be the component: > > UIMA-3881: None > UIMA-3898: Documentation > > I double-checked the issue list, but always for issues for the ruta component. > Forgot to set it when I fixed the issues, sorry. > > Peter > > Am 06.09.2014 23:42, schrieb Marshall Schor: >> Hi, >> >> while testing, I compared the issued fixed (16 issues) with what Jira shows >> (18 >> issues). The 2 issues in Jira which didn't make the issues fixed list (for >> reasons I don't understand) are >> https://issues.apache.org/jira/browse/UIMA-3881 >> and https://issues.apache.org/jira/browse/UIMA-3898 >> >> Any idea why these were not picked up in the build? In my local >> build-from-source, these two issues are also not there. >> >> -Marshall >> > > >
