[jira] [Updated] (UIMA-5209) Some external service pingers left running after shutdown

[ https://issues.apache.org/jira/browse/UIMA-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5209: - Fix Version/s: (was: 2.2.0-Ducc) future-DUCC Needs investigation > Some exter

[jira] [Updated] (UIMA-5227) Customized user logging fails in DUCC Job Driver

[ https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5227: - Fix Version/s: (was: 2.2.0-Ducc) future-DUCC > Customized user logging fa

[jira] [Created] (UIMA-5227) Customized user logging fails in DUCC Job Driver

Burn Lewis created UIMA-5227: Summary: Customized user logging fails in DUCC Job Driver Key: UIMA-5227 URL: https://issues.apache.org/jira/browse/UIMA-5227 Project: UIMA Issue Type: Bug

[jira] [Resolved] (UIMA-5183) Support "fenced-off" worker nodes with read-only access to DUCC_HOME

[ https://issues.apache.org/jira/browse/UIMA-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5183. -- Resolution: Fixed Use a node-specific configuration file if it exists, e.g. use resources/abc123

[jira] [Closed] (UIMA-5183) Support "fenced-off" worker nodes with read-only access to DUCC_HOME

[ https://issues.apache.org/jira/browse/UIMA-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5183. > Support "fenced-off" worker nodes with read-only access

[jira] [Updated] (UIMA-5190) DUCC's RM logs too much

[ https://issues.apache.org/jira/browse/UIMA-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5190: - Fix Version/s: (was: 2.2.0-Ducc) future-DUCC > DUCC's RM logs too m

[jira] [Created] (UIMA-5221) DUCC start script should not start duplicate agents

Burn Lewis created UIMA-5221: Summary: DUCC start script should not start duplicate agents Key: UIMA-5221 URL: https://issues.apache.org/jira/browse/UIMA-5221 Project: UIMA Issue Type: Bug

[jira] [Reopened] (UIMA-5208) Also search the classpath and datapath when loading an extenal overrides file

[ https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5208: -- Must update docs > Also search the classpath and datapath when loading an extenal overrides f

[jira] [Updated] (UIMA-5208) Also search the classpath and datapath when loading an extenal overrides file

[ https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5208: - Fix Version/s: 3.0.0SDKexp > Also search the classpath and datapath when loading an extenal overrides f

Re: [VOTE] Release UIMA-AS 2.9.0 RC2

- downloaded binary tarball and checked md5 & sha1 sums - unpacked, ran MeetingDetector as in README section 3.4 - also deployed with deployAsyncService and ran runRemoteAsyncAE from another node - installed in DUCC and ran a long test with 5 DUCC jobs using 3 UIMA-AS services. - verified that it

[jira] [Created] (UIMA-5214) Add option to restrict vertical scaling of DUCC service instances

Burn Lewis created UIMA-5214: Summary: Add option to restrict vertical scaling of DUCC service instances Key: UIMA-5214 URL: https://issues.apache.org/jira/browse/UIMA-5214 Project: UIMA Issue

[jira] [Resolved] (UIMA-5208) Also search the classpath and datapath when loading an extenal overrides file

[ https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5208. -- Resolution: Fixed Use the RelativePathResolver to load from the datapath or classpath if the settings

[jira] [Closed] (UIMA-5208) Also search the classpath and datapath when loading an extenal overrides file

[ https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5208. > Also search the classpath and datapath when loading an extenal overrides f

[jira] [Updated] (UIMA-5177) NPEs occur if Saxon is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5177: - Summary: NPEs occur if Saxon is in the classpath (was: NPEs occur if Saxon9 is in the classpath) > N

[jira] [Commented] (UIMA-5177) NPEs occur if Saxon9 is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15738871#comment-15738871 ] Burn Lewis commented on UIMA-5177: -- No, quite similar to my results on Linux ... I saw the first (which

[jira] [Closed] (UIMA-5177) NPEs occur if Saxon9 is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5177. > NPEs occur if Saxon9 is in the classpath > > >

[jira] [Closed] (UIMA-4856) DUCC broker should be restricted to ducc use only

[ https://issues.apache.org/jira/browse/UIMA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-4856. Also provided an unsecure configuration for ducc-sim as it uses the DUCC broker as an application broker

[jira] [Resolved] (UIMA-4856) DUCC broker should be restricted to ducc use only

[ https://issues.apache.org/jira/browse/UIMA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-4856. -- Resolution: Fixed Assignee: Burn Lewis Modified broker configuration > DUCC broker sho

[jira] [Updated] (UIMA-4856) DUCC broker should be restricted to ducc use only

[ https://issues.apache.org/jira/browse/UIMA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-4856: - Fix Version/s: (was: future-DUCC) 2.2.0-Ducc > DUCC broker should be restric

[jira] [Created] (UIMA-5199) UIMA-AS should check for a core UIMA version no older than it

Burn Lewis created UIMA-5199: Summary: UIMA-AS should check for a core UIMA version no older than it Key: UIMA-5199 URL: https://issues.apache.org/jira/browse/UIMA-5199 Project: UIMA Issue Type

Re: [VOTE] Release UIMA-AS 2.9.0 RC1

In examples/.classpath I see: but the jar is named: apache-activemq/lib/optional/xpp3-1.1.4c.jar On Sun, Dec 4, 2016 at 10:27 AM, Jaroslaw Cwiklik wrote: > Hmm, looks like a hole in my testing script I don't import runtime > configurations from uimaj-examples. I

Re: [VOTE] Release UIMA-AS 2.9.0 RC1

But what is the purpose of this test? Currently it expects the major version numbers to match, and prints a misleading error message if they don't. Are we sure that UIMA-AS 2.9.0 will work with any V2 UIMA? Or should the test be for the version of core UIMA that UIMA-AS includes, and has been

[jira] [Closed] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5117. > UIMA-AS: dd2spring should log at INFO > - > >

[jira] [Closed] (UIMA-5126) UIMA-AS thows an NPE if saxon9he.jar is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5126. > UIMA-AS thows an NPE if saxon9he.jar is in the classp

[jira] [Created] (UIMA-5190) DUCC's RM logs too much

Burn Lewis created UIMA-5190: Summary: DUCC's RM logs too much Key: UIMA-5190 URL: https://issues.apache.org/jira/browse/UIMA-5190 Project: UIMA Issue Type: Bug Components: DUCC

[jira] [Created] (UIMA-5183) Support "fenced-off" worker nodes with read-only access to DUCC_HOME

Burn Lewis created UIMA-5183: Summary: Support "fenced-off" worker nodes with read-only access to DUCC_HOME Key: UIMA-5183 URL: https://issues.apache.org/jira/browse/UIMA-5183 Pro

[jira] [Created] (UIMA-5182) ducc-mon should hide/show other large values when displaying Job, AP, or Service specifications

Burn Lewis created UIMA-5182: Summary: ducc-mon should hide/show other large values when displaying Job, AP, or Service specifications Key: UIMA-5182 URL: https://issues.apache.org/jira/browse/UIMA-5182

[jira] [Commented] (UIMA-5177) NPEs occur if Saxon9 is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654175#comment-15654175 ] Burn Lewis commented on UIMA-5177: -- Spec says that the the startElement arguments localName and qName can

[jira] [Work started] (UIMA-5177) NPEs occur if Saxon9 is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-5177 started by Burn Lewis. > NPEs occur if Saxon9 is in the classp

[jira] [Created] (UIMA-5177) NPEs occur if Saxon9 is in the classpath

Burn Lewis created UIMA-5177: Summary: NPEs occur if Saxon9 is in the classpath Key: UIMA-5177 URL: https://issues.apache.org/jira/browse/UIMA-5177 Project: UIMA Issue Type: Bug

[jira] [Updated] (UIMA-5170) When pages have "no data" indicate if because not logged in or data missing

[ https://issues.apache.org/jira/browse/UIMA-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5170: - Summary: When pages have "no data" indicate if because not logged in or data missing (wa

[jira] [Created] (UIMA-5170) Improve handling of Experiments and other pages when not logged in

Burn Lewis created UIMA-5170: Summary: Improve handling of Experiments and other pages when not logged in Key: UIMA-5170 URL: https://issues.apache.org/jira/browse/UIMA-5170 Project: UIMA Issue

[jira] [Created] (UIMA-5152) DUCC may let a JP grab some WIs if pre-empted just as initilization completes

Burn Lewis created UIMA-5152: Summary: DUCC may let a JP grab some WIs if pre-empted just as initilization completes Key: UIMA-5152 URL: https://issues.apache.org/jira/browse/UIMA-5152 Project: UIMA

[jira] [Created] (UIMA-5150) Duplicate agents (or daemons) MUST be avoided

Burn Lewis created UIMA-5150: Summary: Duplicate agents (or daemons) MUST be avoided Key: UIMA-5150 URL: https://issues.apache.org/jira/browse/UIMA-5150 Project: UIMA Issue Type: Bug

[jira] [Created] (UIMA-5146) Multiple pipelines need to share just the resources in a ResourceManager

Burn Lewis created UIMA-5146: Summary: Multiple pipelines need to share just the resources in a ResourceManager Key: UIMA-5146 URL: https://issues.apache.org/jira/browse/UIMA-5146 Project: UIMA

[jira] [Closed] (UIMA-4837) When a nodepool is empty a job will just say WaitingForResources

[ https://issues.apache.org/jira/browse/UIMA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-4837. > When a nodepool is empty a job will just say WaitingForResour

[jira] [Updated] (UIMA-5075) DUCC should check that it runs with the uid of the installer

[ https://issues.apache.org/jira/browse/UIMA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5075: - Fix Version/s: (was: future-DUCC) 2.2.0-Ducc > DUCC should check that it r

[jira] [Closed] (UIMA-5075) DUCC should check that it runs with the uid of the installer

[ https://issues.apache.org/jira/browse/UIMA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5075. > DUCC should check that it runs with the uid of the instal

[jira] [Closed] (UIMA-5080) DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd

[ https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5080. > DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete

[jira] [Updated] (UIMA-5080) DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd

[ https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5080: - Fix Version/s: (was: future-DUCC) 2.2.0-Ducc > DUCC uses UIMA-AS's dd2spring.

[jira] [Updated] (UIMA-5124) DUCC-MON doesn't display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5124: - Summary: DUCC-MON doesn't display the Reason for WaitingForResources for jobs (was: DUCC-MON doesn'y

[jira] [Reopened] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5124: -- > DUCC-MON doesn'y display the Reason for WaitingForResources for j

[jira] [Closed] (UIMA-5124) DUCC-MON doesn't display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5124. Resolution: Fixed > DUCC-MON doesn't display the Reason for WaitingForResources for j

[jira] [Updated] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5124: - Fix Version/s: (was: future-DUCC) 2.2.0-Ducc > DUCC-MON doesn'y display the Rea

[jira] [Reopened] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5124: -- > DUCC-MON doesn'y display the Reason for WaitingForResources for j

[jira] [Closed] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5124. Resolution: Fixed > DUCC-MON doesn'y display the Reason for WaitingForResources for j

[jira] [Resolved] (UIMA-5145) DUCC attempts to run even if the DB doesn't start

[ https://issues.apache.org/jira/browse/UIMA-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5145. -- Resolution: Fixed If start_ducc fails to connect to the DB don't start other daemons. DB may

[jira] [Created] (UIMA-5145) DUCC attempts to run even if the DB doesn't start

Burn Lewis created UIMA-5145: Summary: DUCC attempts to run even if the DB doesn't start Key: UIMA-5145 URL: https://issues.apache.org/jira/browse/UIMA-5145 Project: UIMA Issue Type: Bug

[jira] [Updated] (UIMA-5086) DUCC should consider slightly larger machines when reserving a whole machine

[ https://issues.apache.org/jira/browse/UIMA-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5086: - Fix Version/s: (was: future-DUCC) 2.2.0-Ducc > DUCC should consider slightly lar

[jira] [Resolved] (UIMA-5086) DUCC should consider slightly larger machines when reserving a whole machine

[ https://issues.apache.org/jira/browse/UIMA-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5086. -- Resolution: Fixed After rounding up a reserve request consider machines up to ducc.rm.reserve_overage

[jira] [Comment Edited] (UIMA-5126) UIMA-AS thows an NPE if saxon9he.jar is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1812#comment-1812 ] Burn Lewis edited comment on UIMA-5126 at 10/7/16 6:12 PM: --- Problem starts

[jira] [Commented] (UIMA-5126) UIMA-AS thows an NPE if saxon9he.jar is in the classpath

[ https://issues.apache.org/jira/browse/UIMA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1812#comment-1812 ] Burn Lewis commented on UIMA-5126: -- Problem starts with: class load: javax/xml/transform/FactoryFinder

[jira] [Created] (UIMA-5134) DUCC should verify that the version of ducc_ling is compatible

Burn Lewis created UIMA-5134: Summary: DUCC should verify that the version of ducc_ling is compatible Key: UIMA-5134 URL: https://issues.apache.org/jira/browse/UIMA-5134 Project: UIMA Issue

[jira] [Created] (UIMA-5126) UIMA-AS thows an NPE if saxon9he.jar is in the classpath

Burn Lewis created UIMA-5126: Summary: UIMA-AS thows an NPE if saxon9he.jar is in the classpath Key: UIMA-5126 URL: https://issues.apache.org/jira/browse/UIMA-5126 Project: UIMA Issue Type: Bug

[jira] [Resolved] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5117. -- Resolution: Fixed Added a check for the saxon version as if saxon9 is in the classpath dd2spring

[jira] [Reopened] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5117: -- dd2spring will fail if saxon9 is in the user's classpath as the command-line syntax has been changed

[jira] [Closed] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5124. > DUCC-MON doesn'y display the Reason for WaitingForResources for j

[jira] [Resolved] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

[ https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5124. -- Resolution: Fixed Set the reason for jobs waiting for resources > DUCC-MON doesn'y display the Rea

[jira] [Created] (UIMA-5124) DUCC-MON doesn'y display the Reason for WaitingForResources for jobs

Burn Lewis created UIMA-5124: Summary: DUCC-MON doesn'y display the Reason for WaitingForResources for jobs Key: UIMA-5124 URL: https://issues.apache.org/jira/browse/UIMA-5124 Project: UIMA

[jira] [Resolved] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5117. -- Resolution: Fixed Log errors at SEVERE level. Use a shutdown hook to report when saxon calls exit

[jira] [Closed] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5117. > UIMA-AS: dd2spring should log at INFO > - > >

[jira] [Reopened] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5117: -- Assignee: Burn Lewis (was: Jerry Cwiklik) Perhaps better to log these failures as SEVERE. Also would

[jira] [Commented] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514328#comment-15514328 ] Burn Lewis commented on UIMA-5117: -- Since this is a serious error shouldn't we log at SEVERE rather than

Re: opinion on degree of backwards compatibility for Uima V3 experiment

Could the id assigned in V3 be the same as the V2 address, as if the offset in a heap? Unique and monotonically increasing. Burn On Fri, Sep 2, 2016 at 5:36 AM, Peter Klügl wrote: > Same here. > > > It looks like that we are now also starting to use the address, and

Re: UimaContextHolderTest is not a JUnit test?

It is run 3 times by TestAnnotator2 which is run by a JUnit test. On Wed, Aug 31, 2016 at 11:56 AM, Marshall Schor wrote: > The class UimaContextHolderTest isn't a JUnit test, and therefore doesn't > get > run with the testing framework. > > Should this be converted to a JUnit

[jira] [Created] (UIMA-5088) UIMA-AS getmeta fails with an old http broker (the one in UIMA-AS 2.6)

Burn Lewis created UIMA-5088: Summary: UIMA-AS getmeta fails with an old http broker (the one in UIMA-AS 2.6) Key: UIMA-5088 URL: https://issues.apache.org/jira/browse/UIMA-5088 Project: UIMA

[jira] [Created] (UIMA-5087) DUCC pinger fails with http service

Burn Lewis created UIMA-5087: Summary: DUCC pinger fails with http service Key: UIMA-5087 URL: https://issues.apache.org/jira/browse/UIMA-5087 Project: UIMA Issue Type: Bug Components

[jira] [Updated] (UIMA-4921) Implement horizontal stacking of work to maximize CPU usage across cluster

[ https://issues.apache.org/jira/browse/UIMA-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-4921: - Description: APs should be put on the "least-loaded" machine. Base load on the % mem

[jira] [Created] (UIMA-5086) DUCC should consider slightly larger machines when reserving a whole machine

Burn Lewis created UIMA-5086: Summary: DUCC should consider slightly larger machines when reserving a whole machine Key: UIMA-5086 URL: https://issues.apache.org/jira/browse/UIMA-5086 Project: UIMA

[jira] [Resolved] (UIMA-5080) DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd

[ https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5080. -- Resolution: Fixed Edit UIMA-AS's dd2spring ... will be a no-op when UIMA-AS is fixed. > DUCC uses U

[jira] [Work started] (UIMA-5080) DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd

[ https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-5080 started by Burn Lewis. > DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete

[jira] [Updated] (UIMA-5080) DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd

[ https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5080: - Assignee: Burn Lewis (was: Jerry Cwiklik) Fix Version/s: (was: 2.8.1AS

[jira] [Created] (UIMA-5080) DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd

Burn Lewis created UIMA-5080: Summary: DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd Key: UIMA-5080 URL: https://issues.apache.org/jira/browse/UIMA-5080 Project: UIMA

Re: [VOTE] UIMAJ SDK 2.9.0 rc1

- Checked signatures on tar file (would be nice if the files had unix linends) - Tested binary build on a couple of large pipelines - Checked signatures on source zip - Built from source and tested on the same 2 pipelines - Checked notices & licenses - no changes - Tested with UIMA-AS 2.8.1 [X]

[jira] [Resolved] (UIMA-5075) DUCC should check that it runs with the uid of the installer

[ https://issues.apache.org/jira/browse/UIMA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5075. -- Resolution: Fixed start/stop/check_ducc will fail if the invoking userid is not the same as the owner

[jira] [Created] (UIMA-5075) DUCC should check that it runs with the uid of the installer

Burn Lewis created UIMA-5075: Summary: DUCC should check that it runs with the uid of the installer Key: UIMA-5075 URL: https://issues.apache.org/jira/browse/UIMA-5075 Project: UIMA Issue Type

[jira] [Resolved] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5043. -- Resolution: Fixed Although we didn't achieve consensus I've delivered changes to the new method names

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433068#comment-15433068 ] Burn Lewis commented on UIMA-5043: -- With these direct access methods they're not overriding anything

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433040#comment-15433040 ] Burn Lewis commented on UIMA-5043: -- I guess global is too strong ... the Settings are tied to the root

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432988#comment-15432988 ] Burn Lewis commented on UIMA-5043: -- Yes, I'd like to keep Settings as part of the name but perhaps we also

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432984#comment-15432984 ] Burn Lewis commented on UIMA-5043: -- I view them as both useful for configuration ... one is local

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432929#comment-15432929 ] Burn Lewis commented on UIMA-5043: -- re: UimaContextHolder I don't think it is worth hiding the set method

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432901#comment-15432901 ] Burn Lewis commented on UIMA-5043: -- The existing methods are: getConfigParameterValue

Re: [jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

o access individual external override settings > > -- > > > > Key: UIMA-5043 > > URL: https://issues.apache.org/jira/browse/UIMA-5043 > > Project: UIMA > > Issue Type: Improvement > > Com

[jira] [Resolved] (UIMA-5058) Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined

[ https://issues.apache.org/jira/browse/UIMA-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5058. -- Resolution: Fixed Restored the original check-for-matching-descriptions approach but added a cache

[jira] [Reopened] (UIMA-5058) Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined

[ https://issues.apache.org/jira/browse/UIMA-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5058: -- This check-every-type fix is too expensive ... now trying a fix to the caching that should make

[jira] [Resolved] (UIMA-5058) Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined

[ https://issues.apache.org/jira/browse/UIMA-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5058. -- Resolution: Fixed Assignee: Burn Lewis Check that each new Type/TypePriority/FsIndex already

[jira] [Created] (UIMA-5059) DUCC WS should put jsps into /tmp/ not /tmp/ducc

Burn Lewis created UIMA-5059: Summary: DUCC WS should put jsps into /tmp/ not /tmp/ducc Key: UIMA-5059 URL: https://issues.apache.org/jira/browse/UIMA-5059 Project: UIMA Issue Type: Bug

[jira] [Created] (UIMA-5058) Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined

Burn Lewis created UIMA-5058: Summary: Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined Key: UIMA-5058 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419389#comment-15419389 ] Burn Lewis commented on UIMA-5043: -- I'd prefer to keep the current interface ... and it would be safe

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417182#comment-15417182 ] Burn Lewis commented on UIMA-5043: -- I've tried putting the functions on UIMAFramework (since the other

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415904#comment-15415904 ] Burn Lewis commented on UIMA-5043: -- Nice. We could make the framework set the thread-local UimaContext

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414116#comment-15414116 ] Burn Lewis commented on UIMA-5043: -- My view is that there are use cases for both types of scopes, global

[jira] [Commented] (UIMA-5043) Provide method to access individual external override settings

[ https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15413606#comment-15413606 ] Burn Lewis commented on UIMA-5043: -- The default set of external overrides is loaded from the files

[jira] [Commented] (UIMA-5022) Some Dd2Spring errors are lost and confusing

[ https://issues.apache.org/jira/browse/UIMA-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411866#comment-15411866 ] Burn Lewis commented on UIMA-5022: -- For some reason these changes are not linked to this Jira src

[jira] [Closed] (UIMA-5022) Some Dd2Spring errors are lost and confusing

[ https://issues.apache.org/jira/browse/UIMA-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5022. Resolution: Fixed Listed changes > Some Dd2Spring errors are lost and confus

[jira] [Reopened] (UIMA-5022) Some Dd2Spring errors are lost and confusing

[ https://issues.apache.org/jira/browse/UIMA-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5022: -- > Some Dd2Spring errors are lost and confus

[jira] [Closed] (UIMA-5022) Some Dd2Spring errors are lost and confusing

[ https://issues.apache.org/jira/browse/UIMA-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5022. Resolution: Fixed Corrected fix version > Some Dd2Spring errors are lost and confus

[jira] [Updated] (UIMA-5022) Some Dd2Spring errors are lost and confusing

[ https://issues.apache.org/jira/browse/UIMA-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5022: - Fix Version/s: (was: 2.9.0SDK) 2.8.2AS > Some Dd2Spring errors are l

[jira] [Reopened] (UIMA-5022) Some Dd2Spring errors are lost and confusing

[ https://issues.apache.org/jira/browse/UIMA-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5022: -- > Some Dd2Spring errors are lost and confus

<    1   2   3   4   5   6   7   8   9   10   >