Build failed in Jenkins: UIMA-Ruta-v3 #34

See -- [...truncated 2.54 MB...] [INFO] [INFO] >>> cobertura-maven-plugin:2.7:cobertura (default-cli) > [cobertura]test @ ruta >>> [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce

[jira] [Created] (UIMA-5700) DUCC pull-service wrapper should not always kill the process when a work-item fails

Burn Lewis created UIMA-5700: Summary: DUCC pull-service wrapper should not always kill the process when a work-item fails Key: UIMA-5700 URL: https://issues.apache.org/jira/browse/UIMA-5700 Project:

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

See

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

See

Re: Design choices for changing type systems with loaded JCas classes [was Re: UIMAv3 & WebAnno}

> Some use cases with comments: > > 1) Type T loaded with features f1, f2, f3, JCas loaded with f1, f2, f3 > Followed by: Type T loaded with features f1, f3. > > This causes at the 2nd Type T commit time, the augmentation of type T with > feature f2. > But, the (current) impl just does an

Re: Design choices for changing type systems with loaded JCas classes [was Re: UIMAv3 & WebAnno}

Another "failure" use case: - Load type T, with feature f1.  - Load JCas for type T with feature f2.  --  (merged type T has f1, f2, used to assign offsets) Next, load type T with features f1, and f3. - At commit, this would be "merged" with the JCas, to give f1, f3, and f2. - But f2 already has

Re: Design choices for changing type systems with loaded JCas classes [was Re: UIMAv3 & WebAnno}

The initial implementation requires features in the type system have an ordering that is consistent with what got assigned when the JCas was loaded. Some use cases with comments: 1) Type T loaded with features f1, f2, f3,  JCas loaded with f1, f2, f3 Followed by: Type T loaded with features f1,

Jenkins build is back to normal : UIMA-DUCC #1305

See

Jenkins build is back to normal : UIMA-DUCC » Apache UIMA DUCC: uima-ducc-web #1305

See

[jira] [Closed] (UIMA-5699) DUCC Web Server (WS) should use Resource Manager (RM) calculated value for machine's memory available

[ https://issues.apache.org/jira/browse/UIMA-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-5699. -- > DUCC Web Server (WS) should use Resource Manager (RM) calculated value for > machine's memory available >

[jira] [Resolved] (UIMA-5699) DUCC Web Server (WS) should use Resource Manager (RM) calculated value for machine's memory available

[ https://issues.apache.org/jira/browse/UIMA-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro resolved UIMA-5699. Resolution: Fixed Change set delivered. > DUCC Web Server (WS) should use Resource Manager (RM)

[jira] [Work started] (UIMA-5699) DUCC Web Server (WS) should use Resource Manager (RM) calculated value for machine's memory available

[ https://issues.apache.org/jira/browse/UIMA-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-5699 started by Lou DeGenaro. -- > DUCC Web Server (WS) should use Resource Manager (RM) calculated value for >

[jira] [Created] (UIMA-5699) DUCC Web Server (WS) should use Resource Manager (RM) calculated value for machine's memory available

Lou DeGenaro created UIMA-5699: -- Summary: DUCC Web Server (WS) should use Resource Manager (RM) calculated value for machine's memory available Key: UIMA-5699 URL: https://issues.apache.org/jira/browse/UIMA-5699