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

See Changes: [schor] [maven-release-plugin] prepare for next development iteration [schor] [maven-release-plugin] prepare release uimaj-eclipse-update-site-3.0.0-beta [schor] [UIMA-5613] cleanup pom to use relative

Re: testing uv3 with ...?

On 11.10.2017, at 16:01, Marshall Schor wrote: > > fixed in trunk. Thanks for testing :-) > > On 10/11/2017 9:50 AM, Marshall Schor wrote: >> I think I found the cause: a faulty implementation of load(asInputStream, >> aCAS, >> typeSystem). >> >> Looking at the code, the 3rd

Build failed in Jenkins: UIMA-uimaFIT v3 #62

See -- [...truncated 3.99 MB...] /home/jenkins/jenkins-slave/maven-repositories/1/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar

[jira] [Comment Edited] (UIMA-5611) UIMA-DUCC: Agent fails to kill a child process sometimes

[ https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200450#comment-16200450 ] Jerry Cwiklik edited comment on UIMA-5611 at 10/11/17 9:03 PM: --- An agent

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

[ https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200947#comment-16200947 ] Jerry Cwiklik commented on UIMA-5562: - John, I was able to reproduce the problem. The workaround for

[VOTE] uimaj sdk 3.0.0 beta rc4

Here's RC4 for uimaj-sdk 3.0.0-beta. The fixes since the recent rc3 are UIMA-5584 and newer; you can view all 77 Jiras for this version here: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012310570%20AND%20fixVersion%20%3D%2012339590%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Jenkins build is back to normal : UIMA-Ruta-v3 #10

See

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

See -- [...truncated 3.05 MB...] [INFO] artifact org.eclipse.equinox:common: checking for updates from averbis-osgi-releases [INFO] artifact org.eclipse.equinox:common: checking for updates

Re: [jira] [Created] (UIMA-5614) support Eclipse Jar signing in build

my browser glitched - 5614 is a dup of 5613.  I just deleted the 5614 issue completely. -Marshall On 10/11/2017 10:20 AM, Marshall Schor (JIRA) wrote: > Marshall Schor created UIMA-5614: > > > Summary: support Eclipse Jar signing in build >

[jira] [Deleted] (UIMA-5614) support Eclipse Jar signing in build

[ https://issues.apache.org/jira/browse/UIMA-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor deleted UIMA-5614: - > support Eclipse Jar signing in build > > >

[jira] [Comment Edited] (UIMA-5611) UIMA-DUCC: Agent fails to kill a child process sometimes

[ https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200450#comment-16200450 ] Jerry Cwiklik edited comment on UIMA-5611 at 10/11/17 3:28 PM: --- An agent

[jira] [Commented] (UIMA-5611) UIMA-DUCC: Agent fails to kill a child process sometimes

[ https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200450#comment-16200450 ] Jerry Cwiklik commented on UIMA-5611: - An agent should check status of a process after kill -9 is

[jira] [Created] (UIMA-5615) DUCC's WaitingForDriver should not include the JD initialization phase

Burn Lewis created UIMA-5615: Summary: DUCC's WaitingForDriver should not include the JD initialization phase Key: UIMA-5615 URL: https://issues.apache.org/jira/browse/UIMA-5615 Project: UIMA

[jira] [Created] (UIMA-5614) support Eclipse Jar signing in build

Marshall Schor created UIMA-5614: Summary: support Eclipse Jar signing in build Key: UIMA-5614 URL: https://issues.apache.org/jira/browse/UIMA-5614 Project: UIMA Issue Type: Bug

[jira] [Created] (UIMA-5613) support Eclipse Jar signing in build

Marshall Schor created UIMA-5613: Summary: support Eclipse Jar signing in build Key: UIMA-5613 URL: https://issues.apache.org/jira/browse/UIMA-5613 Project: UIMA Issue Type: Bug

Re: testing uv3 with ...?

fixed in trunk.  Thanks for testing :-) -Marshall On 10/11/2017 9:50 AM, Marshall Schor wrote: > I think I found the cause: a faulty implementation of load(asInputStream, > aCAS, > typeSystem). > > Looking at the code, the 3rd argument is not used!  It looks like something > happened when

Re: testing uv3 with ...?

I think I found the cause: a faulty implementation of load(asInputStream, aCAS, typeSystem). Looking at the code, the 3rd argument is not used!  It looks like something happened when migrating from V2 -> V3 code base, because it's OK in the v2 code base.  Maybe I can blame the cat (she sometimes