Am 07.09.2014 01:49, schrieb Marshall Schor:
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".
I'll take a look.
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...)
Yes, I really should have done it before. Everytime I had the chance,
there were always more important things to do or to prepare.
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?
The best and cleanest solution would be to exchange felix by tycho,
which is able to resolve dependencies using p2 repositories. I was
hoping that felix will sometime support this, too. Actually, I haven't
checked for a year or something if it does now.
Experienced users would be able to build ruta even without Richard's
repository, but it is not really straightforward. I would call it a
"convenience solution".
Just to mention it: There is some discussion on the dltk-dev mailing
list about their current state since the main developers do not have the
time to maintain the project. Could be that we sometime in future need
to exchange the backbone of the Ruta Workbench (maybe with someting like
xtext). This is quite some work and I hope it doesn't come to this.
Peter
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
