You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Peter Klügl <pe...@averbis.com> on 2019/01/15 16:49:05 UTC
[VOTE] Release UIMA Ruta 2.7.0 RC1
Hi,
the first release candidate of Apache UIMA Ruta v2.7.0 is ready for voting.
This minor release is not compatible with UIMA v3
Major changes in this release:
UIMA Ruta Language and Analysis Engine:
* New language feature: label expressions at actions for directly
assigning/reusing newly created annotations. Example: Document{-> a:T1,
CREATE(T2, "ref" = a)};
* New language feature: new type of rule element for completely optional
match which does not require an existing annotation and therefore also
works at the boundary of a window/document. Example: NUM _{-PARTOF(CW)};
* Type lists can be used as matching condition.
* Initial default value of string and annotations variables is now null.
* Comparison of annotation and annotation list are now supported.
* New configuration parameter 'inferenceVisitors'.
* New configuration parameter 'maxRuleMatches'.
* New configuration parameter 'maxRuleElementMatches'.
* New configuration parameter 'rulesScriptName'.
* Inlined rules as condition are only evaluated if the rule element
match was successful.
* Multiple inlined rule blocks are allowed at one rule element.
* String features with allowed values are supported.
* PlainTextAnnotator supports vertical tabs.
* Various improvements for WORDTABLE.
* Thrown exceptions include script name.
* Fixed values of label for failed matches.
* Fixed inlined rules as condition at wildcards.
* Fixed resetting of annotation-based variables.
* Fixed various bugs of wildcards.
* Fixed CONTAINS condition for annotations overlapping the window.
* Fixed COUNT condition.
* Fixed setting variables by configuration parameter.
UIMA Ruta Workbench:
* Query View support more CAS formats.
* Fixed order of scripts in Applied Rules view.
* Fixed reporting of non-existing problems in editor.
Staging repository:
https://repository.apache.org/content/repositories/orgapacheuima-1212/
SVN tag:
https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.7.0
Update site:
https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/
Archive with all sources:
https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/ruta-2.7.0-source-release.zip
Overall 43 issues have been fixed for this release (3 with other resolution)
They can be found in the RELEASE_NOTES.html.
... and here:
https://issues.apache.org/jira/issues/?filter=12345332&jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
Please vote on release:
[ ] +1 OK to release
[ ] 0 Don't care
[ ] -1 Not OK to release, because ...
Thanks.
Peter
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
starting review
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Hi,
I just had a quick look at search.maven.org for the dltk bundles, but
haven't found any. (I would prefer to get rid of the complete repo and
not just of just a few artifacts)
I am not up to date, but I think the best way would be to resolve the
artifact not with an m2 but with a p2 repository meaning directly with
an update site.
I do not know if felix does now support that. It hasn't the last time I
looked. I would have to change the bundle build to tycho with a manifest
first approach, but would require quite some effort.
I really like to get rid of the custom repo... but I have to find the
time to do so. There are also many problems with the eclipse plugins
which require some attention and are postponed for now. The current
release is more about the language and the analysis engine.
Best,
Peter
Am 04.02.2019 um 16:41 schrieb Marshall Schor:
> one other item to take a look at:
>
> The build requires access to a repository at averbis, I think. Ideally, it
> should only require maven repo access. I believe the other repo was to cover
> some issues involving access to Eclipse artifacts, not in Maven. However, I
> think recently that (more) Eclipse artifacts are now in Maven, so it may be
> possible to build with these, instead of averbis?
>
> -Marshall
>
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
one other item to take a look at:
The build requires access to a repository at averbis, I think. Ideally, it
should only require maven repo access. I believe the other repo was to cover
some issues involving access to Eclipse artifacts, not in Maven. However, I
think recently that (more) Eclipse artifacts are now in Maven, so it may be
possible to build with these, instead of averbis?
-Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
Yes, I can reproduce... looks like although the files are there, the artifacts and
Looks like a bug that has mostly gone unnoticed...
Thanks for reporting... hope your build works; if not I'm around to help debug :-)
-Marshall
On 1/28/2019 9:54 AM, Peter Klügl wrote:
> Yes, I only see 2.10.3 on our official update site.
>
>
> For Ruta: I will update the update site for RC1
>
>
> Peter
>
>
> Am 28.01.2019 um 15:51 schrieb Marshall Schor:
>> Hi Peter,
>>
>> Re: the Uima V2:
>>
>> Here's the intent:
>> To have 2.10.2 and 2.10.3 on our official update site.
>> To have the older versions here:
>>
>> http://archive.apache.org/dist/uima/archive-eclipse-update-site/uimaj-2.3.1-2.10.1/
>>
>> I did a quick look at the official one, and see 2 releases (2.10.2 and 2.10.3);
>>
>> What did you observe when testing? Did the update site not have 2.10.2 when
>> actually used?
>>
>> -Marshall
>>
>> On 1/28/2019 4:07 AM, Peter Klügl wrote:
>>> Ah ok.
>>>
>>>
>>> Yes, this was not intentional.
>>>
>>>
>>> I thought that the condition did work even if the property is missing
>>> since the build downloaded the old bundles. So, I thought the default is
>>> 'false'.
>>>
>>>
>>> How should we proceed?
>>>
>>>
>>> I can build a new update site with the same staged artifacts since the
>>> update site build is still a separate/manual step in the release process.
>>>
>>> I could also do a new RC2.
>>>
>>> Or we proceed and accept that the older versions are missing. For me,
>>> this is not a problem. in my opinion, the users should install the
>>> latest version anyway. And we could fix this for the next release.
>>>
>>>
>>> Btw, when I was testing this, I observed the same issue for the uimaj v2
>>> bundles in our official update site.
>>>
>>>
>>> Best,
>>>
>>>
>>> Peter
>>>
>>>
>>>
>>> Am 25.01.2019 um 20:05 schrieb Marshall Schor:
>>>> to see this, uncheck the "Show only the latest versions of available software".
>>>>
>>>> For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions
>>>>
>>>> 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1
>>>>
>>>> for the new update site, only 2.7.0
>>>>
>>>> This isn't necessarily a bad thing, see
>>>> https://uima.apache.org/dev-eclipse-plugin-archiving.
>>>>
>>>> But it seems it wasn't intentional.
>>>> What has gone wrong is that the update site build pom needs to add a property:
>>>> <dropPrevVersions>false</dropPrevVersions>
>>>>
>>>> If not specified, it is defaulting to true in the pom test on line 154 in the
>>>> eclipse-update-site's pom.xml.
>>>>
>>>> -Marshall
>>>>
>>>> On 1/25/2019 1:50 PM, Peter Klügl wrote:
>>>>> Hi,
>>>>>
>>>>>
>>>>> this should not have changed. I see 2.1.0 and later bundles for the staged
>>>>> update site:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
>>>>>
>>>>>
>>>>>
>>>>> I have not checked if it is possible install older version during my review.
>>>>>
>>>>> What do you mean exactly? The update process in Eclispe?
>>>>>
>>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>>
>>>>> Peter
>>>>>
>>>>>
>>>>> Am 25.01.2019 um 19:46 schrieb Marshall Schor:
>>>>>> The eclipse update site no longer has any previous release versions of the
>>>>>> plugins.
>>>>>>
>>>>>> Is this intentional?
>>>>>>
>>>>>> -Marshall
>>>>>>
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Yes, I only see 2.10.3 on our official update site.
For Ruta: I will update the update site for RC1
Peter
Am 28.01.2019 um 15:51 schrieb Marshall Schor:
> Hi Peter,
>
> Re: the Uima V2:
>
> Here's the intent:
> To have 2.10.2 and 2.10.3 on our official update site.
> To have the older versions here:
>
> http://archive.apache.org/dist/uima/archive-eclipse-update-site/uimaj-2.3.1-2.10.1/
>
> I did a quick look at the official one, and see 2 releases (2.10.2 and 2.10.3);
>
> What did you observe when testing? Did the update site not have 2.10.2 when
> actually used?
>
> -Marshall
>
> On 1/28/2019 4:07 AM, Peter Klügl wrote:
>> Ah ok.
>>
>>
>> Yes, this was not intentional.
>>
>>
>> I thought that the condition did work even if the property is missing
>> since the build downloaded the old bundles. So, I thought the default is
>> 'false'.
>>
>>
>> How should we proceed?
>>
>>
>> I can build a new update site with the same staged artifacts since the
>> update site build is still a separate/manual step in the release process.
>>
>> I could also do a new RC2.
>>
>> Or we proceed and accept that the older versions are missing. For me,
>> this is not a problem. in my opinion, the users should install the
>> latest version anyway. And we could fix this for the next release.
>>
>>
>> Btw, when I was testing this, I observed the same issue for the uimaj v2
>> bundles in our official update site.
>>
>>
>> Best,
>>
>>
>> Peter
>>
>>
>>
>> Am 25.01.2019 um 20:05 schrieb Marshall Schor:
>>> to see this, uncheck the "Show only the latest versions of available software".
>>>
>>> For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions
>>>
>>> 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1
>>>
>>> for the new update site, only 2.7.0
>>>
>>> This isn't necessarily a bad thing, see
>>> https://uima.apache.org/dev-eclipse-plugin-archiving.
>>>
>>> But it seems it wasn't intentional.
>>> What has gone wrong is that the update site build pom needs to add a property:
>>> <dropPrevVersions>false</dropPrevVersions>
>>>
>>> If not specified, it is defaulting to true in the pom test on line 154 in the
>>> eclipse-update-site's pom.xml.
>>>
>>> -Marshall
>>>
>>> On 1/25/2019 1:50 PM, Peter Klügl wrote:
>>>> Hi,
>>>>
>>>>
>>>> this should not have changed. I see 2.1.0 and later bundles for the staged
>>>> update site:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
>>>>
>>>>
>>>>
>>>> I have not checked if it is possible install older version during my review.
>>>>
>>>> What do you mean exactly? The update process in Eclispe?
>>>>
>>>>
>>>>
>>>> Best,
>>>>
>>>>
>>>> Peter
>>>>
>>>>
>>>> Am 25.01.2019 um 19:46 schrieb Marshall Schor:
>>>>> The eclipse update site no longer has any previous release versions of the
>>>>> plugins.
>>>>>
>>>>> Is this intentional?
>>>>>
>>>>> -Marshall
>>>>>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
Hi Peter,
Re: the Uima V2:
Here's the intent:
To have 2.10.2 and 2.10.3 on our official update site.
To have the older versions here:
http://archive.apache.org/dist/uima/archive-eclipse-update-site/uimaj-2.3.1-2.10.1/
I did a quick look at the official one, and see 2 releases (2.10.2 and 2.10.3);
What did you observe when testing? Did the update site not have 2.10.2 when
actually used?
-Marshall
On 1/28/2019 4:07 AM, Peter Klügl wrote:
> Ah ok.
>
>
> Yes, this was not intentional.
>
>
> I thought that the condition did work even if the property is missing
> since the build downloaded the old bundles. So, I thought the default is
> 'false'.
>
>
> How should we proceed?
>
>
> I can build a new update site with the same staged artifacts since the
> update site build is still a separate/manual step in the release process.
>
> I could also do a new RC2.
>
> Or we proceed and accept that the older versions are missing. For me,
> this is not a problem. in my opinion, the users should install the
> latest version anyway. And we could fix this for the next release.
>
>
> Btw, when I was testing this, I observed the same issue for the uimaj v2
> bundles in our official update site.
>
>
> Best,
>
>
> Peter
>
>
>
> Am 25.01.2019 um 20:05 schrieb Marshall Schor:
>> to see this, uncheck the "Show only the latest versions of available software".
>>
>> For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions
>>
>> 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1
>>
>> for the new update site, only 2.7.0
>>
>> This isn't necessarily a bad thing, see
>> https://uima.apache.org/dev-eclipse-plugin-archiving.
>>
>> But it seems it wasn't intentional.
>> What has gone wrong is that the update site build pom needs to add a property:
>> <dropPrevVersions>false</dropPrevVersions>
>>
>> If not specified, it is defaulting to true in the pom test on line 154 in the
>> eclipse-update-site's pom.xml.
>>
>> -Marshall
>>
>> On 1/25/2019 1:50 PM, Peter Klügl wrote:
>>> Hi,
>>>
>>>
>>> this should not have changed. I see 2.1.0 and later bundles for the staged
>>> update site:
>>>
>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
>>>
>>>
>>>
>>> I have not checked if it is possible install older version during my review.
>>>
>>> What do you mean exactly? The update process in Eclispe?
>>>
>>>
>>>
>>> Best,
>>>
>>>
>>> Peter
>>>
>>>
>>> Am 25.01.2019 um 19:46 schrieb Marshall Schor:
>>>> The eclipse update site no longer has any previous release versions of the
>>>> plugins.
>>>>
>>>> Is this intentional?
>>>>
>>>> -Marshall
>>>>
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
Hi,
I would suggest rebuilding the update site, and posting the release as RC1a or
something in your email, with an explanation :-).
I would rather that pruning the releases is more methodical/intentional, with
the older ones still being available at the
archive.apache.org/dist/uima/archive-eclipse-update-site/ruta-x.x.x-y.y.y site.
My experience is that users may have use cases we don't think of which could
require access to an older version (but not usually) - so the archive serves a
purpose.
Thanks. -Marshall
On 1/28/2019 4:07 AM, Peter Klügl wrote:
> Ah ok.
>
>
> Yes, this was not intentional.
>
>
> I thought that the condition did work even if the property is missing
> since the build downloaded the old bundles. So, I thought the default is
> 'false'.
>
>
> How should we proceed?
>
>
> I can build a new update site with the same staged artifacts since the
> update site build is still a separate/manual step in the release process.
>
> I could also do a new RC2.
>
> Or we proceed and accept that the older versions are missing. For me,
> this is not a problem. in my opinion, the users should install the
> latest version anyway. And we could fix this for the next release.
>
>
> Btw, when I was testing this, I observed the same issue for the uimaj v2
> bundles in our official update site.
>
>
> Best,
>
>
> Peter
>
>
>
> Am 25.01.2019 um 20:05 schrieb Marshall Schor:
>> to see this, uncheck the "Show only the latest versions of available software".
>>
>> For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions
>>
>> 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1
>>
>> for the new update site, only 2.7.0
>>
>> This isn't necessarily a bad thing, see
>> https://uima.apache.org/dev-eclipse-plugin-archiving.
>>
>> But it seems it wasn't intentional.
>> What has gone wrong is that the update site build pom needs to add a property:
>> <dropPrevVersions>false</dropPrevVersions>
>>
>> If not specified, it is defaulting to true in the pom test on line 154 in the
>> eclipse-update-site's pom.xml.
>>
>> -Marshall
>>
>> On 1/25/2019 1:50 PM, Peter Klügl wrote:
>>> Hi,
>>>
>>>
>>> this should not have changed. I see 2.1.0 and later bundles for the staged
>>> update site:
>>>
>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
>>>
>>>
>>>
>>> I have not checked if it is possible install older version during my review.
>>>
>>> What do you mean exactly? The update process in Eclispe?
>>>
>>>
>>>
>>> Best,
>>>
>>>
>>> Peter
>>>
>>>
>>> Am 25.01.2019 um 19:46 schrieb Marshall Schor:
>>>> The eclipse update site no longer has any previous release versions of the
>>>> plugins.
>>>>
>>>> Is this intentional?
>>>>
>>>> -Marshall
>>>>
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Ah ok.
Yes, this was not intentional.
I thought that the condition did work even if the property is missing
since the build downloaded the old bundles. So, I thought the default is
'false'.
How should we proceed?
I can build a new update site with the same staged artifacts since the
update site build is still a separate/manual step in the release process.
I could also do a new RC2.
Or we proceed and accept that the older versions are missing. For me,
this is not a problem. in my opinion, the users should install the
latest version anyway. And we could fix this for the next release.
Btw, when I was testing this, I observed the same issue for the uimaj v2
bundles in our official update site.
Best,
Peter
Am 25.01.2019 um 20:05 schrieb Marshall Schor:
> to see this, uncheck the "Show only the latest versions of available software".
>
> For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions
>
> 2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1
>
> for the new update site, only 2.7.0
>
> This isn't necessarily a bad thing, see
> https://uima.apache.org/dev-eclipse-plugin-archiving.
>
> But it seems it wasn't intentional.
> What has gone wrong is that the update site build pom needs to add a property:
> <dropPrevVersions>false</dropPrevVersions>
>
> If not specified, it is defaulting to true in the pom test on line 154 in the
> eclipse-update-site's pom.xml.
>
> -Marshall
>
> On 1/25/2019 1:50 PM, Peter Klügl wrote:
>> Hi,
>>
>>
>> this should not have changed. I see 2.1.0 and later bundles for the staged
>> update site:
>>
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
>>
>>
>>
>> I have not checked if it is possible install older version during my review.
>>
>> What do you mean exactly? The update process in Eclispe?
>>
>>
>>
>> Best,
>>
>>
>> Peter
>>
>>
>> Am 25.01.2019 um 19:46 schrieb Marshall Schor:
>>> The eclipse update site no longer has any previous release versions of the
>>> plugins.
>>>
>>> Is this intentional?
>>>
>>> -Marshall
>>>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
to see this, uncheck the "Show only the latest versions of available software".
For the www.apache.org/dist/uima/eclipse-update-site/ruta, you see versions
2.1.0, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4.0, 2.5.0, 2.6.0, 2.6.1
for the new update site, only 2.7.0
This isn't necessarily a bad thing, see
https://uima.apache.org/dev-eclipse-plugin-archiving.
But it seems it wasn't intentional.
What has gone wrong is that the update site build pom needs to add a property:
<dropPrevVersions>false</dropPrevVersions>
If not specified, it is defaulting to true in the pom test on line 154 in the
eclipse-update-site's pom.xml.
-Marshall
On 1/25/2019 1:50 PM, Peter Klügl wrote:
> Hi,
>
>
> this should not have changed. I see 2.1.0 and later bundles for the staged
> update site:
>
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
>
>
>
> I have not checked if it is possible install older version during my review.
>
> What do you mean exactly? The update process in Eclispe?
>
>
>
> Best,
>
>
> Peter
>
>
> Am 25.01.2019 um 19:46 schrieb Marshall Schor:
>> The eclipse update site no longer has any previous release versions of the
>> plugins.
>>
>> Is this intentional?
>>
>> -Marshall
>>
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Hi,
this should not have changed. I see 2.1.0 and later bundles for the
staged update site:
https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/features/
I have not checked if it is possible install older version during my review.
What do you mean exactly? The update process in Eclispe?
Best,
Peter
Am 25.01.2019 um 19:46 schrieb Marshall Schor:
> The eclipse update site no longer has any previous release versions of the plugins.
>
> Is this intentional?
>
> -Marshall
>
--
Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
The eclipse update site no longer has any previous release versions of the plugins.
Is this intentional?
-Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
ok, not a blocker... just mentioned it in case it was overlooked. -Marshall
On 2/1/2019 12:17 PM, Peter Klügl wrote:
> Hi,
>
>
> Am 01.02.2019 um 17:07 schrieb Marshall Schor:
>> Are the new features / changes properly reflected in the ruta-docbook documentation?
>
> Hmm, I do not know if I can answer this question. It depends on the
> interpretation of "properly".
>
>
> I tried to mention/integrate each change in the documentation. The size
> of a diff is not directly proportional to the importance of a new feature.
>
> In my opinion, examples are missing in "Learning by example" for the new
> language features, but "optional" got its own section, "labels at
> actions" is mentioned in the syntax section and the multiple inlined
> rules in its section.
>
> The new configuration parameters are described in the corresponding section.
>
>
> There should be more documentation for the new (and also old) stuff and
> users will certainly require more documentation and especially more
> examples to fully utilize the features. There is also the option to
> provide patches or ask for more documentation in a ticket...
>
>
> I think the documentation has also a problem when comparing the
> structure to its size. I noticed that users have a hard time to find
> specific information in the 120 pages (or they do not even look at it).
> There should maybe be more redundant descriptions in orthogonal
> chapters, more examples and howtos compared to the reference.
>
>
> Best,
>
>
> Peter
>
>
>
>> (A compare of the 2.6.1 and 2.7.0 releases shows just minor changes.)
>>
>> -Marshall
>>
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Hi,
Am 01.02.2019 um 17:07 schrieb Marshall Schor:
> Are the new features / changes properly reflected in the ruta-docbook documentation?
Hmm, I do not know if I can answer this question. It depends on the
interpretation of "properly".
I tried to mention/integrate each change in the documentation. The size
of a diff is not directly proportional to the importance of a new feature.
In my opinion, examples are missing in "Learning by example" for the new
language features, but "optional" got its own section, "labels at
actions" is mentioned in the syntax section and the multiple inlined
rules in its section.
The new configuration parameters are described in the corresponding section.
There should be more documentation for the new (and also old) stuff and
users will certainly require more documentation and especially more
examples to fully utilize the features. There is also the option to
provide patches or ask for more documentation in a ticket...
I think the documentation has also a problem when comparing the
structure to its size. I noticed that users have a hard time to find
specific information in the 120 pages (or they do not even look at it).
There should maybe be more redundant descriptions in orthogonal
chapters, more examples and howtos compared to the reference.
Best,
Peter
> (A compare of the 2.6.1 and 2.7.0 releases shows just minor changes.)
>
> -Marshall
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
Are the new features / changes properly reflected in the ruta-docbook documentation?
(A compare of the 2.6.1 and 2.7.0 releases shows just minor changes.)
-Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
restarting testing :-) after fixup of update site. -Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Aargh! New laptop, forgot to set the maven property...
Best,
Peter
Am 01.02.2019 um 19:43 schrieb Marshall Schor:
> issuesFixed report has headings in German :-)
>
> -Marshall
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
issuesFixed report has headings in German :-)
-Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
update for updated update site ;-)
- old bundles are available - OK
- installed feature in Eclipse Photon - OK
- tested new stuff in Ruta Workbench - OK
[X] +1 OK to release
Peter
Am 16.01.2019 um 10:09 schrieb Peter Klügl:
> - mvn clean install svn-tag - OK
> - mvn clean install source-release - OK
> - tested update site in Eclispe 4.8 (there are known problems in 4.9 and
> 4.10) - OK
> - SHA512 files are present - OK
> - spot checked sigs/checksums - OK
> - tested rc with ruta-based component repos - OK (rules may need to be
> adapted)
>
> [X] +1 OK to release
>
>
> Peter
>
>
> Am 15.01.2019 um 17:49 schrieb Peter Klügl:
>> Hi,
>>
>> the first release candidate of Apache UIMA Ruta v2.7.0 is ready for voting.
>> This minor release is not compatible with UIMA v3
>>
>> Major changes in this release:
>>
>> UIMA Ruta Language and Analysis Engine:
>> * New language feature: label expressions at actions for directly
>> assigning/reusing newly created annotations. Example: Document{-> a:T1,
>> CREATE(T2, "ref" = a)};
>> * New language feature: new type of rule element for completely optional
>> match which does not require an existing annotation and therefore also
>> works at the boundary of a window/document. Example: NUM _{-PARTOF(CW)};
>> * Type lists can be used as matching condition.
>> * Initial default value of string and annotations variables is now null.
>> * Comparison of annotation and annotation list are now supported.
>> * New configuration parameter 'inferenceVisitors'.
>> * New configuration parameter 'maxRuleMatches'.
>> * New configuration parameter 'maxRuleElementMatches'.
>> * New configuration parameter 'rulesScriptName'.
>> * Inlined rules as condition are only evaluated if the rule element
>> match was successful.
>> * Multiple inlined rule blocks are allowed at one rule element.
>> * String features with allowed values are supported.
>> * PlainTextAnnotator supports vertical tabs.
>> * Various improvements for WORDTABLE.
>> * Thrown exceptions include script name.
>> * Fixed values of label for failed matches.
>> * Fixed inlined rules as condition at wildcards.
>> * Fixed resetting of annotation-based variables.
>> * Fixed various bugs of wildcards.
>> * Fixed CONTAINS condition for annotations overlapping the window.
>> * Fixed COUNT condition.
>> * Fixed setting variables by configuration parameter.
>>
>> UIMA Ruta Workbench:
>> * Query View support more CAS formats.
>> * Fixed order of scripts in Applied Rules view.
>> * Fixed reporting of non-existing problems in editor.
>>
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapacheuima-1212/
>>
>> SVN tag:
>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.7.0
>>
>> Update site:
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/
>>
>> Archive with all sources:
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/ruta-2.7.0-source-release.zip
>>
>> Overall 43 issues have been fixed for this release (3 with other resolution)
>> They can be found in the RELEASE_NOTES.html.
>>
>> ... and here:
>>
>> https://issues.apache.org/jira/issues/?filter=12345332&jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>
>> Please vote on release:
>>
>> [ ] +1 OK to release
>> [ ] 0 Don't care
>> [ ] -1 Not OK to release, because ...
>>
>> Thanks.
>>
>> Peter
>>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
- mvn clean install svn-tag - OK
- mvn clean install source-release - OK
- tested update site in Eclispe 4.8 (there are known problems in 4.9 and
4.10) - OK
- SHA512 files are present - OK
- spot checked sigs/checksums - OK
- tested rc with ruta-based component repos - OK (rules may need to be
adapted)
[X] +1 OK to release
Peter
Am 15.01.2019 um 17:49 schrieb Peter Klügl:
> Hi,
>
> the first release candidate of Apache UIMA Ruta v2.7.0 is ready for voting.
> This minor release is not compatible with UIMA v3
>
> Major changes in this release:
>
> UIMA Ruta Language and Analysis Engine:
> * New language feature: label expressions at actions for directly
> assigning/reusing newly created annotations. Example: Document{-> a:T1,
> CREATE(T2, "ref" = a)};
> * New language feature: new type of rule element for completely optional
> match which does not require an existing annotation and therefore also
> works at the boundary of a window/document. Example: NUM _{-PARTOF(CW)};
> * Type lists can be used as matching condition.
> * Initial default value of string and annotations variables is now null.
> * Comparison of annotation and annotation list are now supported.
> * New configuration parameter 'inferenceVisitors'.
> * New configuration parameter 'maxRuleMatches'.
> * New configuration parameter 'maxRuleElementMatches'.
> * New configuration parameter 'rulesScriptName'.
> * Inlined rules as condition are only evaluated if the rule element
> match was successful.
> * Multiple inlined rule blocks are allowed at one rule element.
> * String features with allowed values are supported.
> * PlainTextAnnotator supports vertical tabs.
> * Various improvements for WORDTABLE.
> * Thrown exceptions include script name.
> * Fixed values of label for failed matches.
> * Fixed inlined rules as condition at wildcards.
> * Fixed resetting of annotation-based variables.
> * Fixed various bugs of wildcards.
> * Fixed CONTAINS condition for annotations overlapping the window.
> * Fixed COUNT condition.
> * Fixed setting variables by configuration parameter.
>
> UIMA Ruta Workbench:
> * Query View support more CAS formats.
> * Fixed order of scripts in Applied Rules view.
> * Fixed reporting of non-existing problems in editor.
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapacheuima-1212/
>
> SVN tag:
> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.7.0
>
> Update site:
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/
>
> Archive with all sources:
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/ruta-2.7.0-source-release.zip
>
> Overall 43 issues have been fixed for this release (3 with other resolution)
> They can be found in the RELEASE_NOTES.html.
>
> ... and here:
>
> https://issues.apache.org/jira/issues/?filter=12345332&jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> Peter
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Hi,
sorry, I totally forgot about this issue after the commit problems.
I think it does not need to be resolved. Both are needed and should be
merged (as you described).
The folder "antlr" contains the grammar(s) for parsing the ruta rules
for the analysis engine.
The folder "jflex" is new and contains the lexer grammar for the token
seeding, which was manually generated and put in src/main/java before.
I simply forgot to clean up the pom after including the jflex code gen
in the maven build.
I am not concerned about the artifacts in this rc. They are fine. If
there is a problem pointed out by the warning, hardly anything would work.
I would propose to fix this for the next release.
Best,
Peter
Am 30.01.2019 um 19:13 schrieb Marshall Schor:
> Hi -
>
> did you resolve this issue?
>
> Or does it not need resolving - if so, why?
>
> -Marshall
>
> On 1/25/2019 1:56 PM, Marshall Schor wrote:
>> building from source gives a warning about duplicate declaration of
>> build-helper-maven-plugin in ruta-core.
>>
>> Looking at the pom, there are two xml segments in the <build> for this, one
>> specifying
>> ...generated-sources/antlr3, and the other
>> ...generated-sources/jflex
>>
>> I guess one of these needs to be deleted? or if you need both, they should be
>> in one plugin spec, with two different <executions> having different <id>s.
>>
>> -Marshall
>>
>>
--
Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
Hi -
did you resolve this issue?
Or does it not need resolving - if so, why?
-Marshall
On 1/25/2019 1:56 PM, Marshall Schor wrote:
> building from source gives a warning about duplicate declaration of
> build-helper-maven-plugin in ruta-core.
>
> Looking at the pom, there are two xml segments in the <build> for this, one
> specifying
> ...generated-sources/antlr3, and the other
> ...generated-sources/jflex
>
> I guess one of these needs to be deleted? or if you need both, they should be
> in one plugin spec, with two different <executions> having different <id>s.
>
> -Marshall
>
>
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
building from source gives a warning about duplicate declaration of
build-helper-maven-plugin in ruta-core.
Looking at the pom, there are two xml segments in the <build> for this, one
specifying
...generated-sources/antlr3, and the other
...generated-sources/jflex
I guess one of these needs to be deleted? or if you need both, they should be
in one plugin spec, with two different <executions> having different <id>s.
-Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Hi,
I added it when I was adapting the build process because it was in uimaj
somewhere and I actually wondered why this should be needed. Then, I
simply forgot to remove it.
Best,
Peter
Am 01.02.2019 um 19:36 schrieb Marshall Schor:
> The ruta-parent pom has an extraneous clause:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-gpg-plugin</artifactId>
> <version>1.6</version>
> </plugin>
> <plugin>
>
> This should be removed.
> - It is in the build / plugins section (not plugin-management)
> but specifies no goals or other configuration
>
> - it specifies a version (1.6) but that's already being inherited from the
> apache-wide superpom.
>
> (not a blocker). -Marshall
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
The ruta-parent pom has an extraneous clause:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.6</version>
</plugin>
<plugin>
This should be removed.
- It is in the build / plugins section (not plugin-management)
but specifies no goals or other configuration
- it specifies a version (1.6) but that's already being inherited from the
apache-wide superpom.
(not a blocker). -Marshall
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
This commit was performed to the wrong location although the url was
pointing to dev/. It will take some minutes to clean up the mess.
Am 28.01.2019 um 15:59 schrieb Peter Klügl:
> Hi,
>
>
> I updated the update site for this RC. The artifact and bundles should
> not have changed, but the update site will also allow to install older
> version of the bundles, which are not part of this release vote.
>
>
> Best,
>
>
> Peter
>
>
> Am 15.01.2019 um 17:49 schrieb Peter Klügl:
>> Hi,
>>
>> the first release candidate of Apache UIMA Ruta v2.7.0 is ready for voting.
>> This minor release is not compatible with UIMA v3
>>
>> Major changes in this release:
>>
>> UIMA Ruta Language and Analysis Engine:
>> * New language feature: label expressions at actions for directly
>> assigning/reusing newly created annotations. Example: Document{-> a:T1,
>> CREATE(T2, "ref" = a)};
>> * New language feature: new type of rule element for completely optional
>> match which does not require an existing annotation and therefore also
>> works at the boundary of a window/document. Example: NUM _{-PARTOF(CW)};
>> * Type lists can be used as matching condition.
>> * Initial default value of string and annotations variables is now null.
>> * Comparison of annotation and annotation list are now supported.
>> * New configuration parameter 'inferenceVisitors'.
>> * New configuration parameter 'maxRuleMatches'.
>> * New configuration parameter 'maxRuleElementMatches'.
>> * New configuration parameter 'rulesScriptName'.
>> * Inlined rules as condition are only evaluated if the rule element
>> match was successful.
>> * Multiple inlined rule blocks are allowed at one rule element.
>> * String features with allowed values are supported.
>> * PlainTextAnnotator supports vertical tabs.
>> * Various improvements for WORDTABLE.
>> * Thrown exceptions include script name.
>> * Fixed values of label for failed matches.
>> * Fixed inlined rules as condition at wildcards.
>> * Fixed resetting of annotation-based variables.
>> * Fixed various bugs of wildcards.
>> * Fixed CONTAINS condition for annotations overlapping the window.
>> * Fixed COUNT condition.
>> * Fixed setting variables by configuration parameter.
>>
>> UIMA Ruta Workbench:
>> * Query View support more CAS formats.
>> * Fixed order of scripts in Applied Rules view.
>> * Fixed reporting of non-existing problems in editor.
>>
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapacheuima-1212/
>>
>> SVN tag:
>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.7.0
>>
>> Update site:
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/
>>
>> Archive with all sources:
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/ruta-2.7.0-source-release.zip
>>
>> Overall 43 issues have been fixed for this release (3 with other resolution)
>> They can be found in the RELEASE_NOTES.html.
>>
>> ... and here:
>>
>> https://issues.apache.org/jira/issues/?filter=12345332&jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>
>> Please vote on release:
>>
>> [ ] +1 OK to release
>> [ ] 0 Don't care
>> [ ] -1 Not OK to release, because ...
>>
>> Thanks.
>>
>> Peter
>>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Hi,
I updated the update site for this RC. The artifact and bundles should
not have changed, but the update site will also allow to install older
version of the bundles, which are not part of this release vote.
Best,
Peter
Am 15.01.2019 um 17:49 schrieb Peter Klügl:
> Hi,
>
> the first release candidate of Apache UIMA Ruta v2.7.0 is ready for voting.
> This minor release is not compatible with UIMA v3
>
> Major changes in this release:
>
> UIMA Ruta Language and Analysis Engine:
> * New language feature: label expressions at actions for directly
> assigning/reusing newly created annotations. Example: Document{-> a:T1,
> CREATE(T2, "ref" = a)};
> * New language feature: new type of rule element for completely optional
> match which does not require an existing annotation and therefore also
> works at the boundary of a window/document. Example: NUM _{-PARTOF(CW)};
> * Type lists can be used as matching condition.
> * Initial default value of string and annotations variables is now null.
> * Comparison of annotation and annotation list are now supported.
> * New configuration parameter 'inferenceVisitors'.
> * New configuration parameter 'maxRuleMatches'.
> * New configuration parameter 'maxRuleElementMatches'.
> * New configuration parameter 'rulesScriptName'.
> * Inlined rules as condition are only evaluated if the rule element
> match was successful.
> * Multiple inlined rule blocks are allowed at one rule element.
> * String features with allowed values are supported.
> * PlainTextAnnotator supports vertical tabs.
> * Various improvements for WORDTABLE.
> * Thrown exceptions include script name.
> * Fixed values of label for failed matches.
> * Fixed inlined rules as condition at wildcards.
> * Fixed resetting of annotation-based variables.
> * Fixed various bugs of wildcards.
> * Fixed CONTAINS condition for annotations overlapping the window.
> * Fixed COUNT condition.
> * Fixed setting variables by configuration parameter.
>
> UIMA Ruta Workbench:
> * Query View support more CAS formats.
> * Fixed order of scripts in Applied Rules view.
> * Fixed reporting of non-existing problems in editor.
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapacheuima-1212/
>
> SVN tag:
> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.7.0
>
> Update site:
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/
>
> Archive with all sources:
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/ruta-2.7.0-source-release.zip
>
> Overall 43 issues have been fixed for this release (3 with other resolution)
> They can be found in the RELEASE_NOTES.html.
>
> ... and here:
>
> https://issues.apache.org/jira/issues/?filter=12345332&jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> Peter
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE][CANCELLED] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
Yes, I will take a look.
Am 04.02.2019 um 15:44 schrieb Marshall Schor:
> One additional minor thing to maybe fix, but maybe it's not an issue:
>
> The jflex generate step has a WARNING message about WHITE_SPACE_CHAR not used.
>
> Cheers. -Marshall
>
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
Re: [VOTE][CANCELLED] Release UIMA Ruta 2.7.0 RC1
Posted by Marshall Schor <ms...@schor.com>.
One additional minor thing to maybe fix, but maybe it's not an issue:
The jflex generate step has a WARNING message about WHITE_SPACE_CHAR not used.
Cheers. -Marshall
[VOTE][CANCELLED] Release UIMA Ruta 2.7.0 RC1
Posted by Peter Klügl <pe...@averbis.com>.
This vote for releasing RC1 is cancelled. I will prepare a new RC.
Best,
Peter
Am 15.01.2019 um 17:49 schrieb Peter Klügl:
> Hi,
>
> the first release candidate of Apache UIMA Ruta v2.7.0 is ready for voting.
> This minor release is not compatible with UIMA v3
>
> Major changes in this release:
>
> UIMA Ruta Language and Analysis Engine:
> * New language feature: label expressions at actions for directly
> assigning/reusing newly created annotations. Example: Document{-> a:T1,
> CREATE(T2, "ref" = a)};
> * New language feature: new type of rule element for completely optional
> match which does not require an existing annotation and therefore also
> works at the boundary of a window/document. Example: NUM _{-PARTOF(CW)};
> * Type lists can be used as matching condition.
> * Initial default value of string and annotations variables is now null.
> * Comparison of annotation and annotation list are now supported.
> * New configuration parameter 'inferenceVisitors'.
> * New configuration parameter 'maxRuleMatches'.
> * New configuration parameter 'maxRuleElementMatches'.
> * New configuration parameter 'rulesScriptName'.
> * Inlined rules as condition are only evaluated if the rule element
> match was successful.
> * Multiple inlined rule blocks are allowed at one rule element.
> * String features with allowed values are supported.
> * PlainTextAnnotator supports vertical tabs.
> * Various improvements for WORDTABLE.
> * Thrown exceptions include script name.
> * Fixed values of label for failed matches.
> * Fixed inlined rules as condition at wildcards.
> * Fixed resetting of annotation-based variables.
> * Fixed various bugs of wildcards.
> * Fixed CONTAINS condition for annotations overlapping the window.
> * Fixed COUNT condition.
> * Fixed setting variables by configuration parameter.
>
> UIMA Ruta Workbench:
> * Query View support more CAS formats.
> * Fixed order of scripts in Applied Rules view.
> * Fixed reporting of non-existing problems in editor.
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapacheuima-1212/
>
> SVN tag:
> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.7.0
>
> Update site:
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/eclipse-update-site/ruta/
>
> Archive with all sources:
> https://dist.apache.org/repos/dist/dev/uima/ruta-2.7.0-rc1/ruta-2.7.0-source-release.zip
>
> Overall 43 issues have been fixed for this release (3 with other resolution)
> They can be found in the RELEASE_NOTES.html.
>
> ... and here:
>
> https://issues.apache.org/jira/issues/?filter=12345332&jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.7.0ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> Peter
>
--
Dr. Peter Klügl
R&D Text Mining/Machine Learning
Averbis GmbH
Tennenbacher Str. 11
79106 Freiburg
Germany
Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com
Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó