[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017072#comment-17017072 ] Burn L. Lewis commented on UIMA-5936: - The External Overrides code supports the 4 types of configuration parameters and arrays of them. It uses the valueOf method in the Integer, Float & Boolean classes to convert the string-valued settings, so conversion failures will throw an exception. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.10.5SDK, 3.2.0SDK > > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017000#comment-17017000 ] Richard Eckart de Castilho commented on UIMA-5936: -- When multiple commits are pushed at once, then a build is only triggered for the last commit in the batch - that is why you see some commits without a checkmark. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.10.5SDK, 3.2.0SDK > > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016998#comment-17016998 ] Richard Eckart de Castilho commented on UIMA-5936: -- The checkmark means "All automatic checks have passed". For us, that means the Jenkins PR build did not fail. Click on the checkmark for details. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 2.10.5SDK, 3.2.0SDK > > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016982#comment-17016982 ] Marshall Schor commented on UIMA-5936: -- One more question: The github pull request page for [https://github.com/apache/uima-uimaj/pull/26] has a column in the list of 23 commits right before the last column, where there's sometimes a green check. Any idea what do those checks signify? I'm guessing it indicates a cherry-pick selection included this? > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016981#comment-17016981 ] Richard Eckart de Castilho commented on UIMA-5936: -- Changes that should end up in v2 should always go to master-v2 first. If you made a change in v3 and later figure out it should have been in v2 as well, you'd create a new branch based on v2, cherry-pick the changes from v3 into that branch and then do a PR. After the PR has been merged into v2, v2 should once again be merged into v3 to go back to the desired situation where v2 can easily be merged into v3. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016977#comment-17016977 ] Marshall Schor commented on UIMA-5936: -- For my education: after this, if we make changes to v3 first, and then later want to merge (some of) those into v2, does that confuse things? that is, can the order be swapped? I think the more typical way changes will be introduced in the future is into v3, with some of these "back-ported" to v2. Nice to see a good use of "cherry-picking". > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016821#comment-17016821 ] Richard Eckart de Castilho commented on UIMA-5936: -- I have prepared a [PR-26|https://github.com/apache/uima-uimaj/pull/26] which brings master up-to-date with master-v2 and merges the changes for this issue over in the process. Other commits covered by PR-26 appear to have already been included in master by other means as I did not see any changes related to them in the diff. Once PR-26 has been merged, we can regularly merge master-v2 into master and thereby include enhancements/fixes we prepare for v2 with little effort into v3 as well. E.g. the XML 1.1 stuff that is being discussed elsewhere on this tracker. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016300#comment-17016300 ] Marshall Schor commented on UIMA-5936: -- I don't know. Individual files might be mergable. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016218#comment-17016218 ] Richard Eckart de Castilho commented on UIMA-5936: -- Are we set up to merge master-v2 into master or do you want to have separate PR for v3? > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016079#comment-17016079 ] Marshall Schor commented on UIMA-5936: -- Thanks for all the improvements! :) I merged this into master-v2. I would like to see the same improvements in v3, before we resolve/close this issue. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 50m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014334#comment-17014334 ] Richard Eckart de Castilho commented on UIMA-5936: -- PR has been updated with * backwards compatibility * documentation on the new way of setting parameters * additional unit testing > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Assignee: Richard Eckart de Castilho >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014302#comment-17014302 ] Richard Eckart de Castilho commented on UIMA-5936: -- > probably should be for v3 and maybe also for v2. I'm preparing for v2 and the idea would be to merge v2 into v3 later on and in that way also have it in v3. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014255#comment-17014255 ] Richard Eckart de Castilho commented on UIMA-5936: -- The [External Settings|https://uima.apache.org/d/uimaj-2.10.4/references.html#ugr.ref.xml.component_descriptor.aes.external_configuration_parameter_overrides] support probably also needs to be updated for non-string values at some point... > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014174#comment-17014174 ] Peter Klügl commented on UIMA-5936: --- Yes, I think we need to keep separate methods (if there is no major release) > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014165#comment-17014165 ] Richard Eckart de Castilho commented on UIMA-5936: -- I think it may be best to keep the methods separately, such that the XML serialization code knows whether to serialize parameters using the old or the new XML. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014163#comment-17014163 ] Richard Eckart de Castilho commented on UIMA-5936: -- Question: How should we handle the parameters on the PearSpecifier class? The naive approach would be to have two pairs of parameter getter/setter methods: * get/setParameters (legacy) - only supporting string values * get/setPearParameters (new) - supports arbitrary values If we do this, I wonder whether getPearParameters should also return the parameter values set via the legacy approach... > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012285#comment-17012285 ] Marshall Schor commented on UIMA-5936: -- Great! It also needs some doc updates. > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012235#comment-17012235 ] Marshall Schor commented on UIMA-5936: -- Not sure of the status of this... I see there was a Pull Req #21, now closed, as well as #10. I think neither of these has been updated to address the suggestions in the Pull Req #10 (keep backward compatibility, etc.). Is this correct? > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > Time Spent: 40m > Remaining Estimate: 0h > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862087#comment-16862087 ] Marshall Schor commented on UIMA-5936: -- hi, thanks for this - I've been a bit swamped, but will try to get to this soon (and also your other Jiras :) ) > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858363#comment-16858363 ] Matthias Koch commented on UIMA-5936: - [~schor] What do you think ? > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743960#comment-16743960 ] Matthias Koch commented on UIMA-5936: - i added a patch. should be the same code as the pull request in git > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > Attachments: UIMA-5936.diff > > > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support
[ https://issues.apache.org/jira/browse/UIMA-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724979#comment-16724979 ] Matthias Koch commented on UIMA-5936: - i have added a pull request in github > PearSpecifier should be able to store every parametertype that > analysisEngines support > -- > > Key: UIMA-5936 > URL: https://issues.apache.org/jira/browse/UIMA-5936 > Project: UIMA > Issue Type: Improvement >Affects Versions: 2.10.3SDK >Reporter: Matthias Koch >Priority: Major > > > The pearSpecifier currently holds a Parameter_impl(String, String). This > limits the fields of application. Therefore we changed the specifier to store > an array of nameValuePairs, so all possible analysisEngine parameters are > supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
