[
https://issues.apache.org/jira/browse/UIMA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-434:
---
Attachment: UIMA-434-patch.txt
Contains annotation span modification icons.
More icons will follow lat
[
https://issues.apache.org/jira/browse/UIMA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-422.
---
Resolution: Fixed
> update UIMA DocBook version and Date
>
>
>
[
https://issues.apache.org/jira/browse/UIMA-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-490.
-
Resolution: Fixed
The release has been changed to 2.2.0-incubating except for the Eclipse
plugins,
[
https://issues.apache.org/jira/browse/UIMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-489.
---
Resolution: Cannot Reproduce
I actually can't reproduce the described effect (which was reported to me by
Lev
On 7/5/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Adam - can you look
at Ecore2UimaTypeSystem and see if the "isArrayOrList" method would need
updating?
It looks correct, actually. Since this is converting from an Ecore
model to a UIMA type system, it is in complete control of how the
range
[
https://issues.apache.org/jira/browse/UIMA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-413.
---
Resolution: Fixed
> Allow RunAE to use XMI format XML CAS for input and output
> --
[
https://issues.apache.org/jira/browse/UIMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-491.
---
Resolution: Fixed
> CPE GUI doesn't handle spaces in component descriptor file paths
>
[
https://issues.apache.org/jira/browse/UIMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-491:
---
Assignee: Adam Lally
> CPE GUI doesn't handle spaces in component descriptor file paths
> -
CPE GUI doesn't handle spaces in component descriptor file paths
Key: UIMA-491
URL: https://issues.apache.org/jira/browse/UIMA-491
Project: UIMA
Issue Type: Bug
Compo
release number in wrong format
--
Key: UIMA-490
URL: https://issues.apache.org/jira/browse/UIMA-490
Project: UIMA
Issue Type: Bug
Affects Versions: 2.2
Reporter: Marshall Schor
Assignee
[
https://issues.apache.org/jira/browse/UIMA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reopened UIMA-422:
-
> update UIMA DocBook version and Date
>
>
> Key:
Windows .bat files should use "endlocal" command
Key: UIMA-489
URL: https://issues.apache.org/jira/browse/UIMA-489
Project: UIMA
Issue Type: Bug
Components: Build, Packaging and Test
[
https://issues.apache.org/jira/browse/UIMA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510758
]
Marshall Schor commented on UIMA-483:
-
Eddie remarked that the JNI interface to C++ analytics and the blob
seriali
I am note sure how to create more than one patch at the same time.
So I just attached the new/changed files. I can also apply a patch,
but for this you must apply the other patch first.
On Jul 6, 2007, at 8:39 PM, Marshall Schor (JIRA) wrote:
[ https://issues.apache.org/jira/browse/UIMA-48
[
https://issues.apache.org/jira/browse/UIMA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510757
]
Marshall Schor commented on UIMA-485:
-
Both the AnnotationStyle.java and DrawingStyle.java appear to already be in
[
https://issues.apache.org/jira/browse/UIMA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-413:
Fix Version/s: 2.2
> Allow RunAE to use XMI format XML CAS for input and output
> ---
[
https://issues.apache.org/jira/browse/UIMA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-413:
-
Assignee: Adam Lally (was: Eddie Epstein)
For backwards compatibility should still accept the setting of
[
https://issues.apache.org/jira/browse/UIMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-484.
---
Resolution: Fixed
Fix Version/s: 2.2
> Clean build fails on Saxon download (tmp dir does not exi
CVD doesn't handle Errors that are thrown by an AE
--
Key: UIMA-488
URL: https://issues.apache.org/jira/browse/UIMA-488
Project: UIMA
Issue Type: Bug
Components: Tools
Enviro
[
https://issues.apache.org/jira/browse/UIMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reassigned UIMA-484:
---
Assignee: Marshall Schor
> Clean build fails on Saxon download (tmp dir does not exist)
> -
XCAS operations may slow down when using command line tools
---
Key: UIMA-487
URL: https://issues.apache.org/jira/browse/UIMA-487
Project: UIMA
Issue Type: Improvement
Compone
On 7/6/07, Thilo Goetz (JIRA) wrote:
The character data method of keeping string data in the CAS is obsolete. I'll
see if there are any real dependencies on it, or if we can completely remove
that code.
Well, almost obsolete. The JNI interface to C++ analytics and the blob
serialization me
CVD error message box cannot be closed with OK button
-
Key: UIMA-486
URL: https://issues.apache.org/jira/browse/UIMA-486
Project: UIMA
Issue Type: Bug
Components: Tools
[
https://issues.apache.org/jira/browse/UIMA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-479.
---
Resolution: Fixed
> fix test class names that do not end with "Test"
>
[
https://issues.apache.org/jira/browse/UIMA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reassigned UIMA-479:
---
Assignee: Marshall Schor (was: Michael Baessler)
> fix test class names that do not end with "
[
https://issues.apache.org/jira/browse/UIMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510700
]
Thilo Goetz commented on UIMA-476:
--
Your remarks about the interdependence between the Java and C++ implementations
a
[
https://issues.apache.org/jira/browse/UIMA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reopened UIMA-479:
-
JUNIT failing on Eclipse runs - with warning about no tests found in
org.apache.uima.cas.test.CASTest
[
https://issues.apache.org/jira/browse/UIMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-476.
-
Resolution: Fixed
Assignee: Thilo Goetz (was: Marshall Schor)
> FSArray causes error in SOAP
[
https://issues.apache.org/jira/browse/UIMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-476 stopped by Marshall Schor.
> FSArray causes error in SOAP service
>
>
> Key: UIMA-476
>
[
https://issues.apache.org/jira/browse/UIMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510685
]
Marshall Schor commented on UIMA-476:
-
Some interesting things I found out while researching / fixing this.
1) The
[
https://issues.apache.org/jira/browse/UIMA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-485:
---
Attachment: TextColorDrawingStrategy.java
DrawingStyle.java
AnnotationSt
Cas Editor: Add cas text color annotation drawing strategy
--
Key: UIMA-485
URL: https://issues.apache.org/jira/browse/UIMA-485
Project: UIMA
Issue Type: Improvement
Component
I'm currently uploading the next test level to people.a.o.
When it's done, it will be available in
/home/twgoetz/uima-distributions/2.2/02.
--Thilo
Clean build fails on Saxon download (tmp dir does not exist)
Key: UIMA-484
URL: https://issues.apache.org/jira/browse/UIMA-484
Project: UIMA
Issue Type: Bug
Components: B
[EMAIL PROTECTED] wrote:
>> if (internalStringCode != NULL) {
>> return (String) this.stringList.get(internalStringCode);
>> }
>>
>> If you have traced your code in the debugger and found that this is not
>> used,
>> and instead the String constructor is called as you describe, it w
[
https://issues.apache.org/jira/browse/UIMA-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-480.
-
reviewed
> DocumentAnalyzer interactive mode only eligible if an input data directory is
> specified
> if (internalStringCode != NULL) {
> return (String) this.stringList.get(internalStringCode);
> }
>
> If you have traced your code in the debugger and found that this is not used,
> and instead the String constructor is called as you describe, it would be
> helpful if you could
[
https://issues.apache.org/jira/browse/UIMA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510618
]
Thilo Goetz commented on UIMA-483:
--
That's not really what should happen. There are two ways strings are kept in
the
Error messages would be in the form of AnnotatorProcessExceptions,
which you already catch. It might be a good idea to catch Exceptions
in general at that point (I mean unchecked exceptions as well).
Maybe you do that elsewhere. You can look at the corresponding code
in CVD, if you like. It's so
39 matches
Mail list logo
