Marshall Schor (JIRA | 24 May 06:37 2015
Picon

[jira] [Resolved] (UIMA-4428) restore CasCopier alreadyCopied method


     [
https://issues.apache.org/jira/browse/UIMA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-4428.
----------------------------------
    Resolution: Fixed

> restore CasCopier alreadyCopied method
> --------------------------------------
>
>                 Key: UIMA-4428
>                 URL: https://issues.apache.org/jira/browse/UIMA-4428
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.7.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.7.1SDK
>
>
> The redo of the CasCopier inadvertently changed the signature of the alreadyCopied method.  Restore the
2.6.0 version (but keep the 2.7.0 version in case anyone started depending on that one).

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Marshall Schor (JIRA | 24 May 06:24 2015
Picon

[jira] [Created] (UIMA-4428) restore CasCopier alreadyCopied method

Marshall Schor created UIMA-4428:
------------------------------------

             Summary: restore CasCopier alreadyCopied method
                 Key: UIMA-4428
                 URL: https://issues.apache.org/jira/browse/UIMA-4428
             Project: UIMA
          Issue Type: Bug
          Components: Core Java Framework
    Affects Versions: 2.7.0SDK
            Reporter: Marshall Schor
            Assignee: Marshall Schor
             Fix For: 2.7.1SDK

The redo of the CasCopier inadvertently changed the signature of the alreadyCopied method.  Restore the
2.6.0 version (but keep the 2.7.0 version in case anyone started depending on that one).

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Picon

[jira] [Updated] (UIMA-2903) List resources in a ResourceManager / remove hack in uimaFIT


     [
https://issues.apache.org/jira/browse/UIMA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-2903:
---------------------------------------------
    Fix Version/s: 2.3.0uimaFIT

> List resources in a ResourceManager / remove hack in uimaFIT
> ------------------------------------------------------------
>
>                 Key: UIMA-2903
>                 URL: https://issues.apache.org/jira/browse/UIMA-2903
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework, uimaFIT
>            Reporter: Richard Eckart de Castilho
>             Fix For: 2.3.0uimaFIT
>
>
> uimaFIT currently gets a list of resources that are registered with a ResourceManager. This is handled
via accessing the "mResourceMap" field of the ResourceManager_impl class via reflection. Obviously,
this is not a good solution.
> uimaFIT iterates over the resources in the context while initializing resources that are referenced
form other external resources.
> There may be two options:
> # add a listResources() method to the ResourceManager interface
> # get the resources that need to be initialized in some other way. I don't know if there is one, because if
there was, I'd probably have used it. Looking at the  <at> ExternalResource annotations doesn't help,
because they do not give informations about the resource bindings. The bindings are only available in the
(Continue reading)

Picon

[jira] [Updated] (UIMA-3198) Jira change report title is German


     [
https://issues.apache.org/jira/browse/UIMA-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-3198:
---------------------------------------------
    Fix Version/s: 2.2.0uimaFIT

> Jira change report title is German
> ----------------------------------
>
>                 Key: UIMA-3198
>                 URL: https://issues.apache.org/jira/browse/UIMA-3198
>             Project: UIMA
>          Issue Type: Bug
>          Components: uimaFIT
>    Affects Versions: 2.0.0uimaFIT
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Minor
>             Fix For: 2.2.0uimaFIT
>
>
> Jira change report title is German

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Picon

[jira] [Updated] (UIMA-2812) Support ResultSpecification


     [
https://issues.apache.org/jira/browse/UIMA-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-2812:
---------------------------------------------
    Fix Version/s: 2.3.0uimaFIT

> Support ResultSpecification
> ---------------------------
>
>                 Key: UIMA-2812
>                 URL: https://issues.apache.org/jira/browse/UIMA-2812
>             Project: UIMA
>          Issue Type: New Feature
>          Components: uimaFIT
>            Reporter: Richard Eckart de Castilho
>             Fix For: 2.3.0uimaFIT
>
>
> Provide support for controlling the output of a component using a ResultSpecification. Consider the
e.g. use-case that a component can produce a "PartOfSpeech" annotation, but it should not, because
another component in the same pipeline has already produced that or will later produce it. Here some pseudocode:
> {noformat}
> AnalysisEngineDescription aed = createPrimitiveDescription(Parser.class);
> // Tell Parser not to produce PartOfSpeech annotations
> ResultUtil.removeType(aed, PartOfSpeech.class);
> {noformat}
> *How to "remove" a type?* UIMA requires that a ResultSpecification contains _all_ the types that the
component produces, which would normally requiring to add all types except the ones that should not be
(Continue reading)

Picon

[jira] [Updated] (UIMA-3234) Differentiate no Annotation and multiple Annotation case in CasUtil.selectSingle(CAS cas, Type type)


     [
https://issues.apache.org/jira/browse/UIMA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-3234:
---------------------------------------------
    Fix Version/s: 2.2.0uimaFIT

> Differentiate no Annotation and multiple Annotation case in CasUtil.selectSingle(CAS cas, Type type)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-3234
>                 URL: https://issues.apache.org/jira/browse/UIMA-3234
>             Project: UIMA
>          Issue Type: Wish
>          Components: uimaFIT
>    Affects Versions: 2.0.0uimaFIT
>            Reporter: Artem
>            Priority: Trivial
>             Fix For: 2.2.0uimaFIT
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Currently there is one exception type in CasUtil.selectSingle(CAS cas, Type type) method for the case if
CAS does not contain an Annotation or CAS contains more than one Annotation. However, I sometimes need to
differentiate between these two cases in exception handling. A new method like,
selectSingleOrNull(...) could solve this problem: return null if no Annotation, RuntimeException if
multiple Annotations.
> Currently to handle this problem I just use CasUtil.select(...) and check for the size of the returned collection.
(Continue reading)

Picon

[jira] [Updated] (UIMA-3317) shell commands to ease the migration to uimaFIT version 2


     [
https://issues.apache.org/jira/browse/UIMA-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-3317:
---------------------------------------------
    Fix Version/s: 2.2.0uimaFIT

> shell commands to ease the migration to uimaFIT version 2
> ---------------------------------------------------------
>
>                 Key: UIMA-3317
>                 URL: https://issues.apache.org/jira/browse/UIMA-3317
>             Project: UIMA
>          Issue Type: Documentation
>          Components: uimaFIT
>            Reporter: Renaud Richardet
>            Assignee: Richard Eckart de Castilho
>            Priority: Minor
>             Fix For: 2.2.0uimaFIT
>
>         Attachments: migrate_to_uimaFIT_2.sh
>
>
> shell commands to ease the migration to uimaFIT version 2 

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Picon

[jira] [Commented] (UIMA-3808) Type detection mechanism not working in Groovy 2.3.0


    [
https://issues.apache.org/jira/browse/UIMA-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557593#comment-14557593
] 

Richard Eckart de Castilho commented on UIMA-3808:
--------------------------------------------------

Fixed upstream.

> Type detection mechanism not working in Groovy 2.3.0
> ----------------------------------------------------
>
>                 Key: UIMA-3808
>                 URL: https://issues.apache.org/jira/browse/UIMA-3808
>             Project: UIMA
>          Issue Type: Bug
>          Components: uimaFIT
>    Affects Versions: 2.0.0uimaFIT
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>
> An issue has been reported on Stackoverflow that the type detection mechanism does not work with Groovy
2.3.0. I could reproduce this problem, with Groovy 2.3.0, but not with a 2.1.x or 2.2.x version. I expect
this to be a Groovy problem, but for the time being, I'll track it here. If the problem can be tracked down to a
problem in the Groovy code, I'll set up an issue on their tracker too and link it here.
> Ref: http://stackoverflow.com/questions/23504261/dkpro-groovy-usage-and-installation-with-uima

--
This message was sent by Atlassian JIRA
(Continue reading)

Picon

[jira] [Updated] (UIMA-3317) shell commands to ease the migration to uimaFIT version 2


     [
https://issues.apache.org/jira/browse/UIMA-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-3317:
---------------------------------------------
    Affects Version/s:     (was: 2.2.0uimaFIT)

> shell commands to ease the migration to uimaFIT version 2
> ---------------------------------------------------------
>
>                 Key: UIMA-3317
>                 URL: https://issues.apache.org/jira/browse/UIMA-3317
>             Project: UIMA
>          Issue Type: Documentation
>          Components: uimaFIT
>            Reporter: Renaud Richardet
>            Assignee: Richard Eckart de Castilho
>            Priority: Minor
>             Fix For: 2.2.0uimaFIT
>
>         Attachments: migrate_to_uimaFIT_2.sh
>
>
> shell commands to ease the migration to uimaFIT version 2 

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Picon

[jira] [Resolved] (UIMA-3808) Type detection mechanism not working in Groovy 2.3.0


     [
https://issues.apache.org/jira/browse/UIMA-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho resolved UIMA-3808.
----------------------------------------------
    Resolution: Done

> Type detection mechanism not working in Groovy 2.3.0
> ----------------------------------------------------
>
>                 Key: UIMA-3808
>                 URL: https://issues.apache.org/jira/browse/UIMA-3808
>             Project: UIMA
>          Issue Type: Bug
>          Components: uimaFIT
>    Affects Versions: 2.0.0uimaFIT
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>
> An issue has been reported on Stackoverflow that the type detection mechanism does not work with Groovy
2.3.0. I could reproduce this problem, with Groovy 2.3.0, but not with a 2.1.x or 2.2.x version. I expect
this to be a Groovy problem, but for the time being, I'll track it here. If the problem can be tracked down to a
problem in the Groovy code, I'll set up an issue on their tracker too and link it here.
> Ref: http://stackoverflow.com/questions/23504261/dkpro-groovy-usage-and-installation-with-uima

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Picon

[jira] [Commented] (UIMA-3928) createExternalResourceDescription() signatures shadowing each other


    [
https://issues.apache.org/jira/browse/UIMA-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557592#comment-14557592
] 

Richard Eckart de Castilho commented on UIMA-3928:
--------------------------------------------------

I fear this may required incompatible changes.

> createExternalResourceDescription() signatures shadowing each other
> -------------------------------------------------------------------
>
>                 Key: UIMA-3928
>                 URL: https://issues.apache.org/jira/browse/UIMA-3928
>             Project: UIMA
>          Issue Type: Bug
>          Components: uimaFIT
>    Affects Versions: 2.0.0uimaFIT
>            Reporter: Richard Eckart de Castilho
>             Fix For: 3.0.0uimaFIT
>
>
> The method 
> {noformat}
> ExternalResourceDescription createExternalResourceDescription(
>   Class<? extends SharedResourceObject> aInterface, 
>   String aUrl, 
>   Object... aParams)
> {noformat}
(Continue reading)


Gmane