Jenkins build is back to normal : UIMA-v3-sdk #435

2019-04-01 Thread Apache Jenkins Server
See

Re: [VOTE] uimaj 3.0.2 rc4

2019-04-01 Thread Marshall Schor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512   3.0.2-rc4 signatures OK compare source-release with svn tag : OK ran document analyzer from bin package, viewed results- OK issues-fixed jira report: OK api-change reports: OK build from sources: OK installed plugins into Eclipse 2018-12 OK

[VOTE] uimaj 3.0.2 rc4

2019-04-01 Thread Marshall Schor
Hi, I fixed the issue with no Jira issues showing up... and redid this release.   There's no other change. >From the previous release note for rc3: This RC removes the change for UIMA-5869 which is being deferred to a later release. It also changed the version number back to 3.0.2 from 3.1.0.

Build failed in Jenkins: UIMA-v3-sdk #434

2019-04-01 Thread Apache Jenkins Server
See Changes: [schor] [maven-release-plugin] rollback the release of uimaj-3.0.2 [schor] [maven-release-plugin] prepare for next development iteration [schor] [maven-release-plugin] prepare release uimaj-3.0.2

[CANCEL][VOTE] UIMA-DUCC 3.0.0 RC5

2019-04-01 Thread Jerry Cwiklik
Cancelling the vote due to bug found by Lou Degenaro. (UIMA-6019) DUCC 3.0.0 system not backwardly with older CLI Thanks to all for testing this RC. -- Jerry Cwiklik Apache UIMA

Re: [VOTE] [REDOING] Uimaj 3.0.2 rc3

2019-04-01 Thread Marshall Schor
Redoing; forgot to change the jira fix version from 3.1.0 to 3.0.2... -Marshall

Re: [VOTE] [REDOING] Uimaj 3.0.2 rc3

2019-04-01 Thread Marshall Schor
For unknown reasons, the Jira issues fixed report seems to have failed. Investigating... -Marshall On 4/1/2019 12:07 PM, Marshall Schor wrote: > Hi, uimaj-3.0.2 rc3 is posted and ready for voting. > > This RC removes the change for UIMA-5869 which is being deferred to a later > release. > > It

[jira] [Resolved] (UIMA-6019) DUCC 3.0.0 system not backwardly compatible with older CLI

2019-04-01 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro resolved UIMA-6019. Resolution: Fixed Change set delivered. > DUCC 3.0.0 system not backwardly compatible with older

[jira] [Closed] (UIMA-6019) DUCC 3.0.0 system not backwardly compatible with older CLI

2019-04-01 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-6019. -- > DUCC 3.0.0 system not backwardly compatible with older CLI >

[jira] [Updated] (UIMA-6019) DUCC 3.0.0 system not backwardly compatible with older CLI

2019-04-01 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro updated UIMA-6019: --- Summary: DUCC 3.0.0 system not backwardly compatible with older CLI (was: compatible ) > DUCC 3.0.0

[jira] [Updated] (UIMA-6019) compatible

2019-04-01 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro updated UIMA-6019: --- Summary: compatible (was: DUCC 3.0.0 system not backwardly with older CLI) > compatible >

[jira] [Work started] (UIMA-6019) DUCC 3.0.0 system not backwardly with older CLI

2019-04-01 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6019 started by Lou DeGenaro. -- > DUCC 3.0.0 system not backwardly with older CLI >

[jira] [Created] (UIMA-6019) DUCC 3.0.0 system not backwardly with older CLI

2019-04-01 Thread Lou DeGenaro (JIRA)
Lou DeGenaro created UIMA-6019: -- Summary: DUCC 3.0.0 system not backwardly with older CLI Key: UIMA-6019 URL: https://issues.apache.org/jira/browse/UIMA-6019 Project: UIMA Issue Type: Task

Build failed in Jenkins: UIMA-v3-sdk #433

2019-04-01 Thread Apache Jenkins Server
See Changes: [schor] [maven-release-plugin] prepare for next development iteration [schor] [maven-release-plugin] prepare release uimaj-eclipse-update-site-3.0.2 --

Build failed in Jenkins: UIMA-v3-sdk #432

2019-04-01 Thread Apache Jenkins Server
See Changes: [schor] [maven-release-plugin] prepare for next development iteration [schor] [maven-release-plugin] prepare release uimaj-3.0.2 [schor] [UIMA-5869] undo this for release 3.0.2 - deferred [schor] no

[VOTE] Uimaj 3.0.2 rc3

2019-04-01 Thread Marshall Schor
Hi, uimaj-3.0.2 rc3 is posted and ready for voting. This RC removes the change for UIMA-5869 which is being deferred to a later release. It also changed the version number back to 3.0.2 from 3.1.0. Other changes from **rc1**: === The implementation of Subiterator was

[jira] [Resolved] (UIMA-6018) uv3 change release number 3.0.2 to 3.1.0

2019-04-01 Thread Marshall Schor (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-6018. -- Resolution: Fixed > uv3 change release number 3.0.2 to 3.1.0 >

[jira] [Updated] (UIMA-5869) The JCas getView method throws CasRuntimeException not CasException

2019-04-01 Thread Marshall Schor (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-5869: - Fix Version/s: (was: 2.10.4SDK) (was: 3.1.0SDK) > The JCas getView

[jira] [Comment Edited] (UIMA-5869) The JCas getView method throws CasRuntimeException not CasException

2019-04-01 Thread Marshall Schor (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806800#comment-16806800 ] Marshall Schor edited comment on UIMA-5869 at 4/1/19 2:54 PM: -- This fix has

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Marshall Schor
in v3, it doesn't matter.   And, in v3, the temporary fs gets garbage-collected, too. -M On 4/1/2019 10:18 AM, Richard Eckart de Castilho wrote: > On 1. Apr 2019, at 15:46, Marshall Schor wrote: >> The way this works, with the default, is as follows: >> a) imagine a bunch of annotations A1,

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Richard Eckart de Castilho
On 1. Apr 2019, at 15:46, Marshall Schor wrote: > > The way this works, with the default, is as follows: > a) imagine a bunch of annotations A1, A2, ... An, all in the annotation > index > b) imagine the bounding annotation is A2 > c) make a copy of A2, but don't add it to the

[jira] [Reopened] (UIMA-6018) uv3 change release number 3.0.2 to 3.1.0

2019-04-01 Thread Marshall Schor (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor reopened UIMA-6018: -- after reversing UIMA-5869 the reason for moving the version to 3.1.0 instead of 3.0.2 went away. 

[jira] [Reopened] (UIMA-5869) The JCas getView method throws CasRuntimeException not CasException

2019-04-01 Thread Marshall Schor (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor reopened UIMA-5869: -- Assignee: Marshall Schor This fix has broken existing implementations, for little or no added

[jira] [Resolved] (UIMA-6001) Problem with matching items in MarkFast with whitespacers visible

2019-04-01 Thread Viorel Morari (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viorel Morari resolved UIMA-6001. - Resolution: Fixed > Problem with matching items in MarkFast with whitespacers visible >

[jira] [Commented] (UIMA-6001) Problem with matching items in MarkFast with whitespacers visible

2019-04-01 Thread Viorel Morari (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806792#comment-16806792 ] Viorel Morari commented on UIMA-6001: - Applied patch. > Problem with matching items in MarkFast with

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Marshall Schor
CasCompare is still kind of a work in progress;  I think eventually it might become "reusable" but that would take more investment than it's had so far. A lot of the debugging things are there because of the state of the code; I've put most of these (I believe) under the control of some early

[jira] [Work started] (UIMA-6001) Problem with matching items in MarkFast with whitespacers visible

2019-04-01 Thread Viorel Morari (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6001 started by Viorel Morari. --- > Problem with matching items in MarkFast with whitespacers visible >

[jira] [Assigned] (UIMA-6001) Problem with matching items in MarkFast with whitespacers visible

2019-04-01 Thread Viorel Morari (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viorel Morari reassigned UIMA-6001: --- Assignee: Viorel Morari (was: Peter Klügl) > Problem with matching items in MarkFast with

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Richard Eckart de Castilho
On 1. Apr 2019, at 14:57, Marshall Schor wrote: > > :-) Thanks for the quick response! -M Well, your mail came when I was just about to review 3.1.0 :) So while I'm at it, here are some comments I had already noted down (non-blockers): - CasCompare is in src/main/java but seems to contain

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Marshall Schor
:-)  Thanks for the quick response! -M

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Richard Eckart de Castilho
> On 1. Apr 2019, at 14:41, Marshall Schor wrote: > > So, unless there are objections, I plan to change UIMA-5869 to fix the > javadocs, and put the revision back to 3.0.2. Fine by me. -- Richard

Re: [VOTE] [CANCELLED] Uimaj 3.1.0 rc2

2019-04-01 Thread Marshall Schor
Hi, After thinking about this, I've come to the conclusion that we did the wrong fix for https://issues.apache.org/jira/browse/UIMA-5869 We should have changed the javadocs to match the implementation, rather than vice-versa, because the there's likely no incremental positive value from