[jira] [Commented] (UIMA-5610) DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation

2017-10-10 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199118#comment-16199118 ] Lou DeGenaro commented on UIMA-5610: Revised SW prereq text. Java JDK 7 or 8. DUCC has been tested and

[jira] [Closed] (UIMA-5610) DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation

2017-10-10 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-5610. -- Resolution: Fixed > DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation >

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

2017-10-10 Thread Jerry Cwiklik (JIRA)
Jerry Cwiklik created UIMA-5611: --- Summary: UIMA-DUCC: Agent fails to kill a child process sometimes Key: UIMA-5611 URL: https://issues.apache.org/jira/browse/UIMA-5611 Project: UIMA Issue

[jira] [Work started] (UIMA-5610) DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation

2017-10-10 Thread Lou DeGenaro (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-5610 started by Lou DeGenaro. -- > DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation >

[jira] [Created] (UIMA-5610) DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation

2017-10-10 Thread Lou DeGenaro (JIRA)
Lou DeGenaro created UIMA-5610: -- Summary: DUCC Web Server (WS) document requirement for JDK vs. JRE for JSP compilation Key: UIMA-5610 URL: https://issues.apache.org/jira/browse/UIMA-5610 Project: UIMA

signing Eclipse Plugins - a proposed approach

2017-10-10 Thread Marshall Schor
I've documented a proposed approach on the website: https://uima.apache.org/dev-eclipse-plugin-signing This can also be reached from the   home page ->     (left nav bar) Eclipse Update Sites ->   Information for developers ->     information about plugin signing The basic idea is a 2

Re: signing Eclipse Plugins - a proposed approach

2017-10-10 Thread Marshall Schor
one improvement - will document shortly on website:   skip step 1 - no need to "prepare-to-sign". Instead, (after a small fix to the normal build) take all the Jars in the target/eus-work/plugins that are *.jar files, and sign these. This is of course, better, in that it doesn't "rebuild them".

Re: testing uv3 with ...?

2017-10-10 Thread Richard Eckart de Castilho
On 10.10.2017, at 22:03, Richard Eckart de Castilho wrote: > > On 09.10.2017, at 16:35, Marshall Schor wrote: >> >> I think this will need a test case - can you provide one? > > I can see the extended error message and will try to produce a reduced unit >

Re: testing uv3 with ...?

2017-10-10 Thread Richard Eckart de Castilho
On 09.10.2017, at 16:35, Marshall Schor wrote: > > I think this will need a test case - can you provide one? I can see the extended error message and will try to produce a reduced unit test. org.apache.uima.cas.CASRuntimeException: Deserializing Compressed Form 6, a type

Re: signing Eclipse Plugins - a proposed approach

2017-10-10 Thread Marshall Schor
First attempt: did a test signing of the 8 jars in the plugin dir.  Didn't succeed - Looks like maybe you need to sign the Jars used for features too.  I'm trying that next.  -Marshall On 10/10/2017 11:43 AM, Marshall Schor wrote: > one improvement - will document shortly on website: > >   skip

Re: testing uv3 with ...?

2017-10-10 Thread Marshall Schor
re: the second failure: (no such element exception) I think that's now fixed in trunk.  -Marshall On 10/10/2017 4:03 PM, Richard Eckart de Castilho wrote: > On 09.10.2017, at 16:35, Marshall Schor wrote: >> I think this will need a test case - can you provide one? > I can see

Re: signing Eclipse Plugins - a proposed approach

2017-10-10 Thread Marshall Schor
second attempt - signed the feature jars, too.  Got the same "unsigned content" warning, but this time I continued, and to my surprise, it asked me if I trusted these certificates (and it showed the Symantec "TEST" signing certificate) - I said yes, and it completed.  So I guess that counts as

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

2017-10-10 Thread Marshall Schor (JIRA)
Marshall Schor created UIMA-5612: Summary: update the uima-wide shared superPOM Key: UIMA-5612 URL: https://issues.apache.org/jira/browse/UIMA-5612 Project: UIMA Issue Type: Improvement

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

2017-10-10 Thread Apache Jenkins Server
See

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

2017-10-10 Thread Burn Lewis (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199493#comment-16199493 ] Burn Lewis commented on UIMA-5611: -- These became defunct processes so kill -9 won't help ... perhaps agent