Re: Deserializing CAS v2 -> v3 + type system change

On 12/1/2017 5:31 PM, Richard Eckart de Castilho wrote: > On 01.12.2017, at 22:16, Richard Eckart de Castilho wrote: >> It looks to me that v3 is rather flexible with respect to assigning IDs to >> FSes (unlike >> v2 where this was bound to the heap organization). It would be

Re: Deserializing CAS v2 -> v3 + type system change

On 12/1/2017 5:39 PM, Richard Eckart de Castilho wrote: > On 01.12.2017, at 22:47, Marshall Schor wrote: >> I'm wondering if some other approach could be done, that would treat these >> kinds >> of use cases specially, and not have to give up the v3 benefits like GC in >> the

Re: Deserializing CAS v2 -> v3 + type system change

On 01.12.2017, at 22:47, Marshall Schor wrote: > > I'm wondering if some other approach could be done, that would treat these > kinds > of use cases specially, and not have to give up the v3 benefits like GC in the > general case. > > A more general question: The v3 approach to

Re: Deserializing CAS v2 -> v3 + type system change

On 01.12.2017, at 22:16, Richard Eckart de Castilho wrote: > > It looks to me that v3 is rather flexible with respect to assigning IDs to > FSes (unlike > v2 where this was bound to the heap organization). It would be great if this > flexibility > could be used in order to

[jira] [Created] (UIMA-5660) uv3 JCas loading superclass test too strong

Marshall Schor created UIMA-5660: Summary: uv3 JCas loading superclass test too strong Key: UIMA-5660 URL: https://issues.apache.org/jira/browse/UIMA-5660 Project: UIMA Issue Type:

Re: Deserializing CAS v2 -> v3 + type system change

On 12/1/2017 4:16 PM, Richard Eckart de Castilho wrote: > On 01.12.2017, at 16:12, Marshall Schor wrote: >> I'm in the middle of things with changes for 3.0.0sdk; could you check out >> the >> 3.0.0-beta tag and change >> in the uimaj-core project, >> Class:

Re: Deserializing CAS v2 -> v3 + type system change

On 01.12.2017, at 16:12, Marshall Schor wrote: > > I'm in the middle of things with changes for 3.0.0sdk; could you check out > the > 3.0.0-beta tag and change > in the uimaj-core project, > Class: org.apache.uima.cas.impl.FSClassRegistry > to comment out the throw clause:

[CANCEL][VOTE] UIMA-AS 2.10.2 RC2

Cancelling the vote due to two bugs found in JMS Listener #1 prevents connection recovery after broker restart. #2 revert a change to JMS Listener which reduced number of JMS consumers to 1 even though scaleout > 1. Thanks to those who spent the time testing this release candidate. Jerry

Re: [VOTE] release uima parent-pom 11 rc1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512   checked out the tag, built ok used this as the superpom for building uimaj-v3, modifying the parent-pom of uimaj-v3 to remove things now in that super pom, built v3 OK [X] +1 OK to release - -Marshall On 12/1/2017 1:54 PM, Marshall Schor

[VOTE] release uima parent-pom 11 rc1

parent-pom-11 rc1 is posted and ready for voting. The changes are documented in this Jira: https://issues.apache.org/jira/projects/UIMA/versions/12327741 This is a pom - only release. The maven staging repo is here: https://repository.apache.org/content/repositories/orgapacheuima-1172/ The svn

[jira] [Resolved] (UIMA-5612) update the uima-wide shared superPOM

[ https://issues.apache.org/jira/browse/UIMA-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-5612. -- Resolution: Fixed > update the uima-wide shared superPOM >

plan to do release for uima-wide build, v 11

Hi, I've finished with the various upgrades for the uima-wide build superpom. I'd like to get this released; does anyone have other things they want / need changed? (see https://issues.apache.org/jira/browse/UIMA-5612 ) I'll probably go ahead a post an RC1 soon; if it needs fixing, that's

[jira] [Commented] (UIMA-5612) update the uima-wide shared superPOM

[ https://issues.apache.org/jira/browse/UIMA-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274637#comment-16274637 ] Marshall Schor commented on UIMA-5612: -- eclipse update site build process updated to support build

Re: Deserializing CAS v2 -> v3 + type system change

To summarize: JCas classes loaded:    X  (extends SX)   SX (extends Annotation) Deserialize a CAS with a type system having:   X (extends Annotation) Alternative use case:   start with empty system,   create a new pipeline from a spec which includes type X (extends Annotation)   have a