Not sure I follow you. I admit that the ignore whitespace option is
less than perfect (it can't seem to handle newlines correctly, which is
a pain).
Yes, even with ignore whitespace set, the Eclipse compare shows every
change in line wrapping that was caused by your reformat. The Java
Should the manual say a sofa named xxx has an associated cas view,
also named xxx, and that these names can be mapped to different
names by containing aggregates or CPE descriptors?
In particular: looking for what to say about cas views versus sofas.
-Marshall
XCAS is used as
a) the generic name for an externalized CAS
b) a specific format for the externalized CAS (not XMI).
In the documentation, should we use XCAS in the (a) sense, or substitute
XMI-formatted-CAS (or another term?) for it?
-Marshall
On 11/16/06, Marshall Schor [EMAIL PROTECTED] wrote:
The docs describe collection readers and cas initializers. The latter
is deprecated - so I'm removing it from the docs.
Complex collection readers are do-able using re-usable AE parts. What
else should I be saying in the docs about this?
Are
I fixed a bug (reported on the forum) that the Annotation Viewer
didn't support the new primitive types. But I'm not so happy with my
fix... it involved a lot of if..else if blocks for each of the
different array types. You can get an idea of how ugly it was to
implement this just by scanning
Adam Lally wrote:
I fixed a bug (reported on the forum) that the Annotation Viewer
didn't support the new primitive types. But I'm not so happy with my
fix... it involved a lot of if..else if blocks for each of the
different array types. You can get an idea of how ugly it was to
implement this
LowLevelCAS.ll_getTypeClass() needs to be updated for the new 2.0 types
---
Key: UIMA-41
URL: http://issues.apache.org/jira/browse/UIMA-41
Project: UIMA
Issue Type: Bug
I was going to answer you can use LowLevelCAS.ll_getTypeClass(int
typeCode) but I see that Bhavani failed to update that method for the
new types. I will have to deal with the same thing in the CVD one of
these days. When I do, I'll go back to the annotation viewer and see if
I can straighten
Need to reduce CAS size overhead per defined type
-
Key: UIMA-42
URL: http://issues.apache.org/jira/browse/UIMA-42
Project: UIMA
Issue Type: Improvement
Components: Core Java
The ';' path separator char is not replaced with OS dependent char in
installed PEAR
-
Key: UIMA-43
URL: http://issues.apache.org/jira/browse/UIMA-43
Project: UIMA
Lev Kozakov (JIRA) wrote:
[ http://issues.apache.org/jira/browse/UIMA-43?page=all ]
Lev Kozakov updated UIMA-43:
Attachment: UIMA-43.patch
The 'universal' path separator is now replaced in all 'action' values during
PEAR installation.
The ';' path
[ http://issues.apache.org/jira/browse/UIMA-43?page=all ]
Lev Kozakov updated UIMA-43:
Attachment: UIMA-20.patch
Both PEAR files are modified to ensure the PEAR Merger test does not fail in
the Apache UIMA environment.
The ';' path separator char is not
[
http://issues.apache.org/jira/browse/UIMA-43?page=comments#action_12450541 ]
Lev Kozakov commented on UIMA-43:
-
Disregard the comment about PEAR files - it's not relevant to this issue.
The ';' path separator char is not replaced with OS
[ http://issues.apache.org/jira/browse/UIMA-20?page=all ]
Adam Lally updated UIMA-20:
---
Attachment: (was: uima.example.DateTime.pear)
PearMerger unit test failure
Key: UIMA-20
URL:
[ http://issues.apache.org/jira/browse/UIMA-20?page=all ]
Adam Lally updated UIMA-20:
---
Attachment: (was: uima.example.RoomNumber.pear)
PearMerger unit test failure
Key: UIMA-20
URL:
15 matches
Mail list logo
