[jira] [Resolved] (UIMA-4677) UV3 Internal support for Feature Structure IDs

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-4677.
--
Resolution: Fixed

> UV3 Internal support for Feature Structure IDs
> --
>
> Key: UIMA-4677
> URL: https://issues.apache.org/jira/browse/UIMA-4677
> Project: UIMA
>  Issue Type: Sub-task
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp
>
>
> Feature Structures have IDs; these show up in externalized formats.  In v2, 
> these were the int heap address. In V3, these are incrementing ints, starting 
> at 1.
> Support is needed for PEARs and for low-level createFS methods to hold onto 
> FSs to prevent them from being garbage collected.  This is provided using a 
> map from IDs to the FS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (UIMA-4677) UV3 Internal support for Feature Structure IDs

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor updated UIMA-4677:
-
Description: 
Feature Structures have IDs; these show up in externalized formats.  In v2, 
these were the int heap address. In V3, these are incrementing ints, starting 
at 1.

Support is needed for PEARs and for low-level createFS methods to hold onto FSs 
to prevent them from being garbage collected.  This is provided using a map 
from IDs to the FS.

  was:
Feature Structures have IDs; these show up in externalized formats.  In v2, 
these were the int heap address. In V3, -these are incrementing ints, starting 
at 1.- these are designed to mimic v2, for backwards compatibility (and to 
support use-cases that rely on IDs as proxies for actual references to FS 
objects).

Support is needed for PEARs and for low-level createFS methods to hold onto FSs 
to prevent them from being garbage collected.  This is provided using a map 
from IDs to the FS.


> UV3 Internal support for Feature Structure IDs
> --
>
> Key: UIMA-4677
> URL: https://issues.apache.org/jira/browse/UIMA-4677
> Project: UIMA
>  Issue Type: Sub-task
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp
>
>
> Feature Structures have IDs; these show up in externalized formats.  In v2, 
> these were the int heap address. In V3, these are incrementing ints, starting 
> at 1.
> Support is needed for PEARs and for low-level createFS methods to hold onto 
> FSs to prevent them from being garbage collected.  This is provided using a 
> map from IDs to the FS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5185) uv3 throw new exception v2 binary delta deserialization

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5185.
--
Resolution: Fixed

> uv3 throw new exception v2 binary delta deserialization 
> 
>
> Key: UIMA-5185
> URL: https://issues.apache.org/jira/browse/UIMA-5185
> Project: UIMA
>  Issue Type: Improvement
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
>Priority: Minor
> Fix For: 3.0.0SDKexp
>
>
> Version 3 models the v2 layout by scanning all reachable FSs; this drops 
> (versus v2) unreachable FSs.  Binary form deltas encode the changes relative 
> to this model. Because the model for v3 doesn't match v2's (due to the 
> omission of unreachable FSs), delta updates can't be handled when reading a 
> v2-generated delta cas into a v3 instance.  
> Throw an exception for this case (using binary deserializing of Delta CASs 
> generated using V2 into a V3 instance).  Document this in the backwards 
> compatibility section.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5194) uv3 delta serializing- handle case where delta is for non-reachable FS

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5194.
--
Resolution: Fixed

> uv3 delta serializing- handle case where delta is for non-reachable FS
> --
>
> Key: UIMA-5194
> URL: https://issues.apache.org/jira/browse/UIMA-5194
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp
>
>
> In version 3 FSs may be unreachable (if not indexed, and if no other FS that 
> is reachable references them).  Serialization only serializes the reachable 
> FSs; it can't find the others. 
> It's possible that some modifications are done to FSs which subsequently are 
> unreachable.  When serializing, these modifications can't be found in the set 
> of known FSs being serialized.  Handle this case by skipping serialization of 
> those modifications.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5201) uv3 support deserialization of v2 binary serializations

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5201.
--
Resolution: Fixed

> uv3 support deserialization of v2 binary serializations
> ---
>
> Key: UIMA-5201
> URL: https://issues.apache.org/jira/browse/UIMA-5201
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp
>
>
> Because v3 has more built-in types, even "identical" type systems (from the 
> user's point of view) are different.  Accomodate this when deserializing v2 
> serialized binary CASs (including compressed form 4 and 6).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5202) uv3 update eclipse plugins to require java 8

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5202.
--
Resolution: Fixed

> uv3 update eclipse plugins to require java 8
> 
>
> Key: UIMA-5202
> URL: https://issues.apache.org/jira/browse/UIMA-5202
> Project: UIMA
>  Issue Type: Bug
>  Components: Eclipse plugins
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp
>
>
> mark the plugins as requiring java 8, not 7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5195) uv3 add capability to test for v2 - v3 compatibility of serialized forms for form6 compression

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5195.
--
Resolution: Fixed

> uv3 add capability to test for v2 - v3 compatibility of serialized forms for 
> form6 compression
> --
>
> Key: UIMA-5195
> URL: https://issues.apache.org/jira/browse/UIMA-5195
> Project: UIMA
>  Issue Type: Test
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDKexp, 2.9.1SDK
>
>
> Add similar capability for form 6 tests that capture and reuse serialization 
> and random number sequences, as was done for form 4, to verify compatibility 
> with v3, and to insure changes don't break ability to read serializations 
> written with older versions.  Refactor some common things with form 4 testing 
> to share.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (UIMA-4682) IntHashSet - reuse removed slots

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor updated UIMA-4682:
-
Fix Version/s: (was: 3.0.0SDKexp)

> IntHashSet - reuse removed slots
> 
>
> Key: UIMA-4682
> URL: https://issues.apache.org/jira/browse/UIMA-4682
> Project: UIMA
>  Issue Type: Improvement
>  Components: Core Java Framework
>Affects Versions: 2.8.1SDK
>Reporter: Marshall Schor
>Assignee: Marshall Schor
>Priority: Minor
>
> This hash map uses a scheme where removed items are marked with a special 
> value.  Improve the impl by having a subsequent add reuse a removed slot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (UIMA-2971) Getters for boolean values in JCas wrappers don't follow common Java naming convention

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor updated UIMA-2971:
-
Fix Version/s: (was: 3.0.0SDKexp)

> Getters for boolean values in JCas wrappers don't follow common Java naming 
> convention
> --
>
> Key: UIMA-2971
> URL: https://issues.apache.org/jira/browse/UIMA-2971
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>
> The getter generated for a boolean feature "XXX" in a JCas wrapper is called 
> "getXXX". It is a common Java convention, that getters for boolean values are 
> called "isXXX".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (UIMA-5203) Docs don't describe how to define config value common to all settings groups

[Jerry Quinn (JIRA)]

Jerry Quinn created UIMA-5203:
-

 Summary: Docs don't describe how to define config value common to 
all settings groups
 Key: UIMA-5203
 URL: https://issues.apache.org/jira/browse/UIMA-5203
 Project: UIMA
  Issue Type: Bug
  Components: Documentation
Reporter: Jerry Quinn
Priority: Minor


Annotator descriptors support defining config parameters common to all settings 
groups.  But it doesn't show how to set a value once for all config groups.  It 
implies that I have to set it N times for each group I configure.

Is that actually required?  Or can the parameter be defined once and shared 
among all settings groups?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5198.
--
Resolution: Fixed

The eclipse update site at http://www.apache.org/dist/uima/eclipse-update-site 
is now corrected, and should work to say that uima-as latest release (at the  
moment) is 2.8.1, not 2.9.0).  Please retest using a "freshly unzipped" Eclipse 
install.

> uima 2.9.0 files missing eclipse update site
> 
>
> Key: UIMA-5198
> URL: https://issues.apache.org/jira/browse/UIMA-5198
> Project: UIMA
>  Issue Type: Question
>  Components: Eclipse plugins
>Affects Versions: 2.9.0SDK
>Reporter: Andreas Korger
>
> the archives of the 2.9.0 release are missing on the eclipse update site, 
> though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (UIMA-5202) uv3 update eclipse plugins to require java 8

[Marshall Schor (JIRA)]

Marshall Schor created UIMA-5202:


 Summary: uv3 update eclipse plugins to require java 8
 Key: UIMA-5202
 URL: https://issues.apache.org/jira/browse/UIMA-5202
 Project: UIMA
  Issue Type: Bug
  Components: Eclipse plugins
Reporter: Marshall Schor
Assignee: Marshall Schor
 Fix For: 3.0.0SDKexp


mark the plugins as requiring java 8, not 7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (UIMA-5201) uv3 support deserialization of v2 binary serializations

[Marshall Schor (JIRA)]

Marshall Schor created UIMA-5201:


 Summary: uv3 support deserialization of v2 binary serializations
 Key: UIMA-5201
 URL: https://issues.apache.org/jira/browse/UIMA-5201
 Project: UIMA
  Issue Type: Bug
  Components: Core Java Framework
Reporter: Marshall Schor
Assignee: Marshall Schor
 Fix For: 3.0.0SDKexp


Because v3 has more built-in types, even "identical" type systems (from the 
user's point of view) are different.  Accomodate this when deserializing v2 
serialized binary CASs (including compressed form 4 and 6).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (UIMA-5200) leak of some meta artifacts prior to release to uima-as eclipse-update site

[Jerry Cwiklik (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jerry Cwiklik closed UIMA-5200.
---
Resolution: Fixed

Not sure how this happened. Somehow I must have deviated from my release script 
and committed changes into the wrong place. I undone the changes using: mvn 
merge -r -11721 ,
where the 11721 is the revision number under which the code was checked in.

> 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)

Re: [jira] [Created] (UIMA-5200) leak of some meta artifacts prior to release to uima-as eclipse-update site

[Jaroslaw Cwiklik]

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
*

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 

-jerry


On Mon, Dec 5, 2016 at 11:31 AM, Marshall Schor (JIRA) 
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)
>

Jenkins build is back to stable : UIMA-AS #463

[Apache Jenkins Server]

See 

Jenkins build is back to stable : UIMA-AS » Apache UIMA-AS: uimaj-as-activemq #463

[Apache Jenkins Server]

See 

[jira] [Comment Edited] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Andreas Korger (JIRA)]

[ 
https://issues.apache.org/jira/browse/UIMA-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722731#comment-15722731
 ] 

Andreas Korger edited comment on UIMA-5198 at 12/5/16 5:29 PM:
---

Thx for the help, skiped the as, now working, doesnt finish partilaly if the as 
ist missing, where trying to install all the uima plugins in eclips, because 
eclipse had totaly crashed, did everything as ever before (install new 
software, eclips update link from uima site) error: artifact not found packages 
2.9.0 ... missing, tried it with neon and mars, updated Java, ... then checked 
the link ...


was (Author: akorger):
Thx for the help, skiped the as, know working, doesnt finish partilaly if the 
as ist missing, where trying to install all the uima plugins in eclips, because 
eclipse had totaly crashed, did everything as ever before (install new 
software, eclips update link from uima site) error: artifact not found packages 
2.9.0 ... missing, tried it with neon and mars, updated Java, ... then checked 
the link ...

> uima 2.9.0 files missing eclipse update site
> 
>
> Key: UIMA-5198
> URL: https://issues.apache.org/jira/browse/UIMA-5198
> Project: UIMA
>  Issue Type: Question
>  Components: Eclipse plugins
>Affects Versions: 2.9.0SDK
>Reporter: Andreas Korger
>
> the archives of the 2.9.0 release are missing on the eclipse update site, 
> though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Andreas Korger (JIRA)]

[ 
https://issues.apache.org/jira/browse/UIMA-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722731#comment-15722731
 ] 

Andreas Korger edited comment on UIMA-5198 at 12/5/16 5:21 PM:
---

Thx for the help, skiped the as, know working, doesnt finish partilaly if the 
as ist missing, where trying to install all the uima plugins in eclips, because 
eclipse had totaly crashed, did everything as ever before (install new 
software, eclips update link from uima site) error: artifact not found packages 
2.9.0 ... missing, tried it with neon and mars, updated Java, ... then checked 
the link ...


was (Author: akorger):
where trying to install the uima plugins in eclips, because eclipse had totaly 
crashed, did everything as ever before (install new software, eclips update 
link from uima site) error: artifact not found packages 2.9.0 ... missing, 
tried it with neon and mars, updated Java, ...

> uima 2.9.0 files missing eclipse update site
> 
>
> Key: UIMA-5198
> URL: https://issues.apache.org/jira/browse/UIMA-5198
> Project: UIMA
>  Issue Type: Question
>  Components: Eclipse plugins
>Affects Versions: 2.9.0SDK
>Reporter: Andreas Korger
>
> the archives of the 2.9.0 release are missing on the eclipse update site, 
> though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Andreas Korger (JIRA)]

[ 
https://issues.apache.org/jira/browse/UIMA-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722731#comment-15722731
 ] 

Andreas Korger edited comment on UIMA-5198 at 12/5/16 4:59 PM:
---

where trying to install the uima plugins in eclips, because eclipse had totaly 
crashed, did everything as ever before (install new software, eclips update 
link from uima site) error: artifact not found packages 2.9.0 ... missing, 
tried it with neon and mars, updated Java, ...


was (Author: akorger):
where trying to install the uima plugins in eclips, because eclipse had totaly 
crashed, did everything as ever before (install new software, eclips update 
link from uima site) error: artifact not found packages 2.9.0 ... missing

> uima 2.9.0 files missing eclipse update site
> 
>
> Key: UIMA-5198
> URL: https://issues.apache.org/jira/browse/UIMA-5198
> Project: UIMA
>  Issue Type: Question
>  Components: Eclipse plugins
>Affects Versions: 2.9.0SDK
>Reporter: Andreas Korger
>
> the archives of the 2.9.0 release are missing on the eclipse update site, 
> though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Andreas Korger (JIRA)]

[ 
https://issues.apache.org/jira/browse/UIMA-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722731#comment-15722731
 ] 

Andreas Korger commented on UIMA-5198:
--

where trying to install the uima plugins in eclips, because eclipse had totaly 
crashed, did everything as ever before (install new software, eclips update 
link from uima site) error: artifact not found packages 2.9.0 ... missing

> uima 2.9.0 files missing eclipse update site
> 
>
> Key: UIMA-5198
> URL: https://issues.apache.org/jira/browse/UIMA-5198
> Project: UIMA
>  Issue Type: Question
>  Components: Eclipse plugins
>Affects Versions: 2.9.0SDK
>Reporter: Andreas Korger
>
> the archives of the 2.9.0 release are missing on the eclipse update site, 
> though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (UIMA-5200) leak of some meta artifacts prior to release to uima-as eclipse-update site

[Marshall Schor (JIRA)]

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)

flaw in release process for Eclipse plugin for uima-as?

[Marshall Schor]

I noticed while looking at recent jira UIMA-5198 that the pending uima-as
release has already partially updated the official uima eclipse update site. 
This partial update was just to the content and artifact metadata, the plugins
were not updated.

These files of course should not be updated until the release is approved.

I'll put in a Jira for this.

-Marshall

[jira] [Commented] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Marshall Schor (JIRA)]

[ 
https://issues.apache.org/jira/browse/UIMA-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722663#comment-15722663
 ] 

Marshall Schor commented on UIMA-5198:
--

What were you trying to install?  If it was the uima-as plugins, we've just 
noticed a flaw in our release mechanism, which may be causing this.  I think 
other plugins are OK, though.

> uima 2.9.0 files missing eclipse update site
> 
>
> Key: UIMA-5198
> URL: https://issues.apache.org/jira/browse/UIMA-5198
> Project: UIMA
>  Issue Type: Question
>  Components: Eclipse plugins
>Affects Versions: 2.9.0SDK
>Reporter: Andreas Korger
>
> the archives of the 2.9.0 release are missing on the eclipse update site, 
> though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (UIMA-5199) UIMA-AS should check for a core UIMA version no older than it

[Burn Lewis (JIRA)]

Burn Lewis created UIMA-5199:


 Summary: UIMA-AS should check for a core UIMA version no older 
than it
 Key: UIMA-5199
 URL: https://issues.apache.org/jira/browse/UIMA-5199
 Project: UIMA
  Issue Type: Bug
  Components: Async Scaleout
Reporter: Burn Lewis
Priority: Minor
 Fix For: 2.9.0AS


Perhaps check that the major is the same and the minor no older.  The 3rd digit 
could be ignored.  The versions will usually be identical since a matching 
version is included in the UIMA-AS package.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (UIMA-5143) Ruta: Launcher fails because classpath is to large

[JIRA]

[ 
https://issues.apache.org/jira/browse/UIMA-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722468#comment-15722468
 ] 

Peter Klügl commented on UIMA-5143:
---

I removed the classpath info from the cmd arguments for now. This will prevent 
that the ResourceManager can find stuff if the script is launched in 
development mode without new vm. This should not be so problematic since 
UIMA-4405 allows now to debug java code when a script is launched, even the 
ruta implementation.

> Ruta: Launcher fails because classpath is to large
> --
>
> Key: UIMA-5143
> URL: https://issues.apache.org/jira/browse/UIMA-5143
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.4.0ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
> Fix For: 2.5.1ruta
>
>
> Launch delegate does not work. Console reports:
> Exception occurred executing command line.
> Cannot run program "C:\Program Files\Java\jdk1.7.0_79\bin\javaw.exe": 
> CreateProcess error=206, Der Dateiname oder die Erweiterung ist zu lang
> This is most likely caused by the extension being too long, caused by a 
> really large classpath (32k chars?).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-4405) Ruta: when debugging a script, the source of imported/exec uimaFIT component is not shown

[JIRA]

 [ 
https://issues.apache.org/jira/browse/UIMA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Klügl resolved UIMA-4405.
---
   Resolution: Fixed
 Assignee: Peter Klügl
Fix Version/s: 2.5.1ruta

fixed

> Ruta: when debugging a script, the source of imported/exec uimaFIT component 
> is not shown
> -
>
> Key: UIMA-4405
> URL: https://issues.apache.org/jira/browse/UIMA-4405
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.3.0ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
> Fix For: 2.5.1ruta
>
>
> When debugging a script with the common UIMA ruta launch config, the source 
> of imported/exec uimaFIT components is not shown. Breakpoints actually work, 
> but are quite useless if the source code is not displayed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (UIMA-5143) Ruta: Launcher fails because classpath is to large

[JIRA]

 [ 
https://issues.apache.org/jira/browse/UIMA-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Klügl resolved UIMA-5143.
---
Resolution: Fixed
  Assignee: Peter Klügl

fixed

> Ruta: Launcher fails because classpath is to large
> --
>
> Key: UIMA-5143
> URL: https://issues.apache.org/jira/browse/UIMA-5143
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.4.0ruta
>Reporter: Peter Klügl
>Assignee: Peter Klügl
> Fix For: 2.5.1ruta
>
>
> Launch delegate does not work. Console reports:
> Exception occurred executing command line.
> Cannot run program "C:\Program Files\Java\jdk1.7.0_79\bin\javaw.exe": 
> CreateProcess error=206, Der Dateiname oder die Erweiterung ist zu lang
> This is most likely caused by the extension being too long, caused by a 
> really large classpath (32k chars?).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[CANCEL][VOTE] Release UIMA-AS 2.9.0 RC1

[Jaroslaw Cwiklik]

Cancelling the vote due to issues found by Eddie and Marshall.

Thanks to all who spent time checking RC1

Jerry

Re: [VOTE] Release UIMA-AS 2.9.0 RC1

[Jaroslaw Cwiklik]

I see, the bug is in the .classpath. For some reason I thought that Eddie
complained about finding this in a launch script (UIMA AS Deploy
Service.launch). I will cancel RC1 soon.

-jerry

On Mon, Dec 5, 2016 at 8:19 AM, Burn Lewis  wrote:

> In examples/.classpath I see:
>   path="UIMA_HOME/apache-activemq/lib/optional/xpp3-1.1.4.c.jar"/>
> but the jar is named:
>  apache-activemq/lib/optional/xpp3-1.1.4c.jar
>
> On Sun, Dec 4, 2016 at 10:27 AM, Jaroslaw Cwiklik 
> wrote:
>
> > Hmm, looks like a hole in my testing script I don't import runtime
> > configurations from uimaj-examples. I only tested the two runtime
> > configurations that are part of uima-as source which are UIMA Run Remote
> > Async AE and UIMA Deploy AS Service. I can launch both from eclipse
> > (Keppler) without an error. I checked the CP and dont see
> xpp3-1.1.4.c.jar
> > typo. Attached are screenshots from my eclipse for both of these launch
> > configurations. Also I went into uimaj-examples and checked UIMA Deploy
> AS
> > Service.launch file:
> >
> > 
> >
> > This looks ok. No idea why you are seeing this typo. Can someone else,
> > check these run configurations to confirm Eddie's observations?
> >
> > -jerry
> >
> > On Sat, Dec 3, 2016 at 10:13 AM, Eddie Epstein 
> > wrote:
> >
> >> After fixing the typo "xpp3-1.1.4.c.jar -> /xpp3-1.1.4c.jar" found a
> >> problem in the "UIMA Deploy AS Service" run configuration: it includes
> the
> >> uimaj-as projects which are not normally present with the examples
> >> project.
> >> After fixing that the Deploy (and the Run Remote) configuration works,
> as
> >> long as the UIMA_HOME env var was defined before starting eclipse.
> >>
> >> The core UIMA run configurations also have the requirement to define
> >> UIMA_HOME in the environment before starting eclipse. Turns out there
> is a
> >> more dynamic approach: use "windows -> preferences -> run/debug ->
> String
> >> Substitution" to set UIMA_HOME as a string substitution, and then change
> >> the use in run configurations from ${env_var:UIMA_HOME} to just
> >> ${UIMA_HOME}.
> >>
> >> On Fri, Dec 2, 2016 at 6:13 PM, Eddie Epstein 
> >> wrote:
> >>
> >> > Downloaded the binary tarball on RHEL 6
> >> > Installed a fresh eclipse, Neon.
> >> > Installed the uima-as-2.9.0 plugins
> >> > Imported the uimaj-examples project and configured UIMA_HOME variable
> >> > ==> Java Build Path problem:
> >> > DescriptionResourcePathLocationType
> >> > Project 'uimaj-examples' is missing required library:
> >> > '/home/eddie/uimas/apache-uima-as-2.9.0/apache-activemq/
> >> > lib/optional/xpp3-1.1.4.c.jar'uimaj-examplesBuild path
> >> > Build Path Problem
> >> >
> >> > There is a typo in the name of that jar.
> >> >
> >> > -1 to release
> >> >
> >> > Eddie
> >> >
> >> >
> >> >
> >> > On Tue, Nov 22, 2016 at 1:10 PM, Jaroslaw Cwiklik  >
> >> > wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> the UIMA-AS 2.9.0 release candidate 1 is ready for voting.
> >> >>
> >> >> This version contains the following fixes:
> >> >>   - Updated to use Activemq 5.14.0
> >> >>   - Added dependency on UIMA SDK 2.9.0
> >> >>   - Fixed http based service connectivity
> >> >>   - Added support for automatic recovery of temp queues after broker
> >> >> restart.
> >> >>   - Fixed per CAS Performance Metrics breakdown
> >> >>   - Fixed per process CPU & RSS reporting
> >> >>   - Fixed example runtime configurations
> >> >>   - Fixed error recovery on exception while deserializing a CAS
> >> >>   - "Pinned" JMX MBeans to a specific deployment to enable orderly
> >> cleanup
> >> >>   - Fixed support of AMQ white listing of packages
> >> >>   - Added support to disable JMX via a new argument
> >> >> -Duima.as.enable.jmx=false
> >> >>   - Fixed dd2spring issues
> >> >>   - Other Bug fixes
> >> >>
> >> >> The list of changes in Jira:
> >> >> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> >> >> 202.9.0AS%20AND%20project%20%3D%20UIMA
> >> >>
> >> >> The source and binary zip/tars are staged to
> >> >> https://dist.apache.org/repos/dist/dev/uima/uima-as/2.9.0/RC1/
> >> >>
> >> >> The Maven artifacts are here:
> >> >> https://repository.apache.org/content/repositories/
> orgapacheuima-1110
> >> >>
> >> >> The SVN tags are here:
> >> >> http://svn.apache.org/repos/asf/uima/uima-as/tags/uima-as-2.9.0/
> >> >>
> >> >> and for the Eclipse Update Site:
> >> >> https://dist.apache.org/repos/dist/dev/uima/eclipse-update-s
> >> ite/uima-as/
> >> >>
> >> >> See http://uima.apache.org/testing-builds.html for suggestions on
> how
> >> to
> >> >> test
> >> >> release candidates.
> >> >>
> >> >> Please vote on release:
> >> >>
> >> >> [ ] +1 OK to release
> >> >> [ ] 0   Don't care
> >> >> [ ] -1 Not OK to release, because ...
> >> >>
> >> >> Thanks
> >> >>
> >> >
> >> >
> >>
> >
> >
>

Re: [VOTE] Release UIMA-AS 2.9.0 RC1

[Eddie Epstein]

and in "UIMA Deploy AS Service.launch" are three lines:





Eddie

On Mon, Dec 5, 2016 at 8:19 AM, Burn Lewis  wrote:

> In examples/.classpath I see:
>   path="UIMA_HOME/apache-activemq/lib/optional/xpp3-1.1.4.c.jar"/>
> but the jar is named:
>  apache-activemq/lib/optional/xpp3-1.1.4c.jar
>
> On Sun, Dec 4, 2016 at 10:27 AM, Jaroslaw Cwiklik 
> wrote:
>
> > Hmm, looks like a hole in my testing script I don't import runtime
> > configurations from uimaj-examples. I only tested the two runtime
> > configurations that are part of uima-as source which are UIMA Run Remote
> > Async AE and UIMA Deploy AS Service. I can launch both from eclipse
> > (Keppler) without an error. I checked the CP and dont see
> xpp3-1.1.4.c.jar
> > typo. Attached are screenshots from my eclipse for both of these launch
> > configurations. Also I went into uimaj-examples and checked UIMA Deploy
> AS
> > Service.launch file:
> >
> > 
> >
> > This looks ok. No idea why you are seeing this typo. Can someone else,
> > check these run configurations to confirm Eddie's observations?
> >
> > -jerry
> >
> > On Sat, Dec 3, 2016 at 10:13 AM, Eddie Epstein 
> > wrote:
> >
> >> After fixing the typo "xpp3-1.1.4.c.jar -> /xpp3-1.1.4c.jar" found a
> >> problem in the "UIMA Deploy AS Service" run configuration: it includes
> the
> >> uimaj-as projects which are not normally present with the examples
> >> project.
> >> After fixing that the Deploy (and the Run Remote) configuration works,
> as
> >> long as the UIMA_HOME env var was defined before starting eclipse.
> >>
> >> The core UIMA run configurations also have the requirement to define
> >> UIMA_HOME in the environment before starting eclipse. Turns out there
> is a
> >> more dynamic approach: use "windows -> preferences -> run/debug ->
> String
> >> Substitution" to set UIMA_HOME as a string substitution, and then change
> >> the use in run configurations from ${env_var:UIMA_HOME} to just
> >> ${UIMA_HOME}.
> >>
> >> On Fri, Dec 2, 2016 at 6:13 PM, Eddie Epstein 
> >> wrote:
> >>
> >> > Downloaded the binary tarball on RHEL 6
> >> > Installed a fresh eclipse, Neon.
> >> > Installed the uima-as-2.9.0 plugins
> >> > Imported the uimaj-examples project and configured UIMA_HOME variable
> >> > ==> Java Build Path problem:
> >> > DescriptionResourcePathLocationType
> >> > Project 'uimaj-examples' is missing required library:
> >> > '/home/eddie/uimas/apache-uima-as-2.9.0/apache-activemq/
> >> > lib/optional/xpp3-1.1.4.c.jar'uimaj-examplesBuild path
> >> > Build Path Problem
> >> >
> >> > There is a typo in the name of that jar.
> >> >
> >> > -1 to release
> >> >
> >> > Eddie
> >> >
> >> >
> >> >
> >> > On Tue, Nov 22, 2016 at 1:10 PM, Jaroslaw Cwiklik  >
> >> > wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> the UIMA-AS 2.9.0 release candidate 1 is ready for voting.
> >> >>
> >> >> This version contains the following fixes:
> >> >>   - Updated to use Activemq 5.14.0
> >> >>   - Added dependency on UIMA SDK 2.9.0
> >> >>   - Fixed http based service connectivity
> >> >>   - Added support for automatic recovery of temp queues after broker
> >> >> restart.
> >> >>   - Fixed per CAS Performance Metrics breakdown
> >> >>   - Fixed per process CPU & RSS reporting
> >> >>   - Fixed example runtime configurations
> >> >>   - Fixed error recovery on exception while deserializing a CAS
> >> >>   - "Pinned" JMX MBeans to a specific deployment to enable orderly
> >> cleanup
> >> >>   - Fixed support of AMQ white listing of packages
> >> >>   - Added support to disable JMX via a new argument
> >> >> -Duima.as.enable.jmx=false
> >> >>   - Fixed dd2spring issues
> >> >>   - Other Bug fixes
> >> >>
> >> >> The list of changes in Jira:
> >> >> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> >> >> 202.9.0AS%20AND%20project%20%3D%20UIMA
> >> >>
> >> >> The source and binary zip/tars are staged to
> >> >> https://dist.apache.org/repos/dist/dev/uima/uima-as/2.9.0/RC1/
> >> >>
> >> >> The Maven artifacts are here:
> >> >> https://repository.apache.org/content/repositories/
> orgapacheuima-1110
> >> >>
> >> >> The SVN tags are here:
> >> >> http://svn.apache.org/repos/asf/uima/uima-as/tags/uima-as-2.9.0/
> >> >>
> >> >> and for the Eclipse Update Site:
> >> >> https://dist.apache.org/repos/dist/dev/uima/eclipse-update-s
> >> ite/uima-as/
> >> >>
> >> >> See http://uima.apache.org/testing-builds.html for suggestions on
> how
> >> to
> >> >> test
> >> >> release candidates.
> >> >>
> >> >> Please vote on release:
> >> >>
> >> >> [ ] +1 OK to release
> >> >> [ ] 0   Don't care
> >> >> [ ] -1 Not OK to release, because ...
> >> >>
> >> >> Thanks
> >> >>
> >> >
> >> >
> >>
> >
> >
>

[jira] [Created] (UIMA-5198) uima 2.9.0 files missing eclipse update site

[Andreas Korger (JIRA)]

Andreas Korger created UIMA-5198:


 Summary: uima 2.9.0 files missing eclipse update site
 Key: UIMA-5198
 URL: https://issues.apache.org/jira/browse/UIMA-5198
 Project: UIMA
  Issue Type: Question
  Components: Eclipse plugins
Affects Versions: 2.9.0SDK
Reporter: Andreas Korger


the archives of the 2.9.0 release are missing on the eclipse update site, 
though plugin can't be installed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Accessing Document Metadata e.g. Title in UIMA

[Soumitra Mazumder]

Hi,
I  am working presently with Solr6.3 and using UIMA annotators for
annotation. I  have ran into a dead end while trying to access document
meta information from UIMA.Is there any way that can help me to get this
information as I  might want to trigger a third party process. I  have
searched the documents for UIMA  but can not get sufficient help on this.

Regards
Soumitra

Re: [VOTE] Release UIMA-AS 2.9.0 RC1

[Burn Lewis]

In examples/.classpath I see:
 
but the jar is named:
 apache-activemq/lib/optional/xpp3-1.1.4c.jar

On Sun, Dec 4, 2016 at 10:27 AM, Jaroslaw Cwiklik  wrote:

> Hmm, looks like a hole in my testing script I don't import runtime
> configurations from uimaj-examples. I only tested the two runtime
> configurations that are part of uima-as source which are UIMA Run Remote
> Async AE and UIMA Deploy AS Service. I can launch both from eclipse
> (Keppler) without an error. I checked the CP and dont see xpp3-1.1.4.c.jar
> typo. Attached are screenshots from my eclipse for both of these launch
> configurations. Also I went into uimaj-examples and checked UIMA Deploy AS
> Service.launch file:
>
> 
>
> This looks ok. No idea why you are seeing this typo. Can someone else,
> check these run configurations to confirm Eddie's observations?
>
> -jerry
>
> On Sat, Dec 3, 2016 at 10:13 AM, Eddie Epstein 
> wrote:
>
>> After fixing the typo "xpp3-1.1.4.c.jar -> /xpp3-1.1.4c.jar" found a
>> problem in the "UIMA Deploy AS Service" run configuration: it includes the
>> uimaj-as projects which are not normally present with the examples
>> project.
>> After fixing that the Deploy (and the Run Remote) configuration works, as
>> long as the UIMA_HOME env var was defined before starting eclipse.
>>
>> The core UIMA run configurations also have the requirement to define
>> UIMA_HOME in the environment before starting eclipse. Turns out there is a
>> more dynamic approach: use "windows -> preferences -> run/debug -> String
>> Substitution" to set UIMA_HOME as a string substitution, and then change
>> the use in run configurations from ${env_var:UIMA_HOME} to just
>> ${UIMA_HOME}.
>>
>> On Fri, Dec 2, 2016 at 6:13 PM, Eddie Epstein 
>> wrote:
>>
>> > Downloaded the binary tarball on RHEL 6
>> > Installed a fresh eclipse, Neon.
>> > Installed the uima-as-2.9.0 plugins
>> > Imported the uimaj-examples project and configured UIMA_HOME variable
>> > ==> Java Build Path problem:
>> > DescriptionResourcePathLocationType
>> > Project 'uimaj-examples' is missing required library:
>> > '/home/eddie/uimas/apache-uima-as-2.9.0/apache-activemq/
>> > lib/optional/xpp3-1.1.4.c.jar'uimaj-examplesBuild path
>> > Build Path Problem
>> >
>> > There is a typo in the name of that jar.
>> >
>> > -1 to release
>> >
>> > Eddie
>> >
>> >
>> >
>> > On Tue, Nov 22, 2016 at 1:10 PM, Jaroslaw Cwiklik 
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> the UIMA-AS 2.9.0 release candidate 1 is ready for voting.
>> >>
>> >> This version contains the following fixes:
>> >>   - Updated to use Activemq 5.14.0
>> >>   - Added dependency on UIMA SDK 2.9.0
>> >>   - Fixed http based service connectivity
>> >>   - Added support for automatic recovery of temp queues after broker
>> >> restart.
>> >>   - Fixed per CAS Performance Metrics breakdown
>> >>   - Fixed per process CPU & RSS reporting
>> >>   - Fixed example runtime configurations
>> >>   - Fixed error recovery on exception while deserializing a CAS
>> >>   - "Pinned" JMX MBeans to a specific deployment to enable orderly
>> cleanup
>> >>   - Fixed support of AMQ white listing of packages
>> >>   - Added support to disable JMX via a new argument
>> >> -Duima.as.enable.jmx=false
>> >>   - Fixed dd2spring issues
>> >>   - Other Bug fixes
>> >>
>> >> The list of changes in Jira:
>> >> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
>> >> 202.9.0AS%20AND%20project%20%3D%20UIMA
>> >>
>> >> The source and binary zip/tars are staged to
>> >> https://dist.apache.org/repos/dist/dev/uima/uima-as/2.9.0/RC1/
>> >>
>> >> The Maven artifacts are here:
>> >> https://repository.apache.org/content/repositories/orgapacheuima-1110
>> >>
>> >> The SVN tags are here:
>> >> http://svn.apache.org/repos/asf/uima/uima-as/tags/uima-as-2.9.0/
>> >>
>> >> and for the Eclipse Update Site:
>> >> https://dist.apache.org/repos/dist/dev/uima/eclipse-update-s
>> ite/uima-as/
>> >>
>> >> See http://uima.apache.org/testing-builds.html for suggestions on how
>> to
>> >> test
>> >> release candidates.
>> >>
>> >> Please vote on release:
>> >>
>> >> [ ] +1 OK to release
>> >> [ ] 0   Don't care
>> >> [ ] -1 Not OK to release, because ...
>> >>
>> >> Thanks
>> >>
>> >
>> >
>>
>
>