[
https://issues.apache.org/jira/browse/UIMA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-279.
---
Resolution: Fixed
fixed
> toXML method of ServiceAlias has an apparent infinite loop
> ---
[
https://issues.apache.org/jira/browse/UIMA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-255.
---
Resolution: Fixed
Software Grant ack; Code checked in.
> Incorporate UIMA C++ framework code into proj
[
https://issues.apache.org/jira/browse/UIMA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-255:
Description:
Under guidance from Ken Coar, we followed this process:
1) sent in the software grant
2)
[
https://issues.apache.org/jira/browse/UIMA-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-268.
-
Resolution: Fixed
I took a look at this - I think these items need to be done by an ASF member.
[
https://issues.apache.org/jira/browse/UIMA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-289.
---
Fixed. Changed == test to equals.
> CasProcessorDeploymentParamsImpl has incorrect equals test argument
Adam Lally wrote:
Hmmm. I think the suggestion is to update our run configurations to
include these, in any case. Would that not work?
Adam Lally (JIRA) wrote:
Eddie said:
So eclipse was already dependent on the external environment to have
UIMA_HOME set. Unless we want to change how logging
[
https://issues.apache.org/jira/browse/UIMA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-295.
---
Resolution: Fixed
Done. If there are objections, I can switch it back. But I think this is an
improvement.
Restore microscope icon as the window icon for our tools
Key: UIMA-295
URL: https://issues.apache.org/jira/browse/UIMA-295
Project: UIMA
Issue Type: Task
Components: Tools
[
https://issues.apache.org/jira/browse/UIMA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-284.
-
Resolution: Fixed
Assignee: Adam Lally (was: Marshall Schor)
Fixed the ones that were obviou
[
https://issues.apache.org/jira/browse/UIMA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-294.
---
Resolution: Fixed
> Sofa mapping failure in mixed CPE pipeline
> --
>
>
Sofa mapping failure in mixed CPE pipeline
--
Key: UIMA-294
URL: https://issues.apache.org/jira/browse/UIMA-294
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Repor
Adam Lally (JIRA) wrote:
Hmmm. I think the suggestion is to update our run configurations to
include these, in any case. Would that not work?
Eddie said:
So eclipse was already dependent on the external environment to have
UIMA_HOME set. Unless we want to change how logging and other VM
argum
On 2/8/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Adam Lally (JIRA) wrote:
> [
https://issues.apache.org/jira/browse/UIMA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
>
> Adam Lally reassigned UIMA-289:
> ---
>
> Assignee: Marsh
Adam Lally (JIRA) wrote:
[
https://issues.apache.org/jira/browse/UIMA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
So it sounds like you (Eddie) are saying the only thing to do here is
documentation, but only as it pertains to the C++ release - are you writing
Adam Lally (JIRA) wrote:
[
https://issues.apache.org/jira/browse/UIMA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-289:
---
Assignee: Marshall Schor (was: Adam Lally)
I changed your fix to instead che
[
https://issues.apache.org/jira/browse/UIMA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-293.
---
Resolution: Fixed
Fixed, using low level CAS API
> If CasCopier's destination CAS is set to a base CAS, annota
Adam Lally (JIRA) wrote:
[ https://issues.apache.org/jira/browse/UIMA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471460 ]
Adam Lally commented on UIMA-292:
-
I'm nearly certain this problem is related to the xinclude s
[
https://issues.apache.org/jira/browse/UIMA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471460
]
Adam Lally commented on UIMA-292:
-
I'm nearly certain this problem is related to the xinclude support that was in
prev
[
https://issues.apache.org/jira/browse/UIMA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471454
]
Thilo Goetz commented on UIMA-292:
--
Sorry, forgot the most important bit: what version of UIMA?
> UIMA incompatible w
[
https://issues.apache.org/jira/browse/UIMA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471453
]
Thilo Goetz commented on UIMA-292:
--
Thanks for reporting this issue. Could you please be more specific what we
need
If CasCopier's destination CAS is set to a base CAS, annotations cannot be
copied.
--
Key: UIMA-293
URL: https://issues.apache.org/jira/browse/UIMA-293
Project: UIMA
[
https://issues.apache.org/jira/browse/UIMA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-289:
---
Assignee: Marshall Schor (was: Adam Lally)
I changed your fix to instead check for the actual CasProce
[
https://issues.apache.org/jira/browse/UIMA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-290.
---
Agree
> Wrong logical connector || when && was intended, CPMEngine
> -
[
https://issues.apache.org/jira/browse/UIMA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein resolved UIMA-287.
Resolution: Fixed
Fixed, until contradictory evidence arises.
> Eliminate required use of UIMACPP_HO
UIMA incompatible with Java Version 6
-
Key: UIMA-292
URL: https://issues.apache.org/jira/browse/UIMA-292
Project: UIMA
Issue Type: Bug
Components: Core Java Framework, Eclipse plugins
E
[
https://issues.apache.org/jira/browse/UIMA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-265.
-
Resolution: Fixed
> impove CAS Multiplier documentation that CAS Multipliers does not work in CVD
[
https://issues.apache.org/jira/browse/UIMA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471413
]
Michael Baessler commented on UIMA-283:
---
OK, I will retest this with the next level.
> CAS Merger example compon
[
https://issues.apache.org/jira/browse/UIMA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler reopened UIMA-265:
---
since the the process() method calls the processAndOutputNewCASes() method, the
documentation chan
[
https://issues.apache.org/jira/browse/UIMA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471403
]
Michael Baessler commented on UIMA-283:
---
When I run the tests with the DocumentAnalyzer all works fine only with
[
https://issues.apache.org/jira/browse/UIMA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-283.
-
Resolution: Fixed
Assignee: Michael Baessler (was: Adam Lally)
I've updated the SimpleTextMerger.xml
[
https://issues.apache.org/jira/browse/UIMA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471409
]
Adam Lally commented on UIMA-283:
-
The reason it works in the DocumentAnalyzer is that the DocumentAnalyzer uses
the F
[
https://issues.apache.org/jira/browse/UIMA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471392
]
Adam Lally commented on UIMA-283:
-
Actually I don't think it matters whether you use the old or the new API. The
exce
[
https://issues.apache.org/jira/browse/UIMA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-260:
Component/s: (was: Build, Packaging and Test)
(was: Examples)
Docume
On 2/8/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
So here's another proposal, sort of amalgamating what Adam and Eddie
have said. We implement a special kind of bag index just for this
purpose, and kind of bag index that users can not define. Such a bag
index is a regular bag index, except tha
On 2/8/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
So here's another proposal, sort of amalgamating what Adam and Eddie
have said. We implement a special kind of bag index just for this
purpose, and kind of bag index that users can not define. Such a bag
index is a regular bag index, except that
Adam Lally wrote:
On 2/8/07, Eddie Epstein <[EMAIL PROTECTED]> wrote:
-TypeSystem: t2 and t3 derive from t1
-User defined sorted index exists for t3
-fs of type t2 added to index -> causes bag index for t2 to be created
-fs of type t1 added to index -> causes bag index for t1 to be created.
On 2/8/07, Eddie Epstein <[EMAIL PROTECTED]> wrote:
-TypeSystem: t2 and t3 derive from t1
-User defined sorted index exists for t3
-fs of type t2 added to index -> causes bag index for t2 to be created
-fs of type t1 added to index -> causes bag index for t1 to be created.
It could make sense
On 2/8/07, Eddie Epstein <[EMAIL PROTECTED]> wrote:
Adam,
Don't you run "- UIMA_uimaj_Core_003 - sofa related test" as described
in the wiki as part of your manual test suite?
Thanks,
Eddie
Nope.
You had given me some examples that used remote sofa mapping, but that
feature is no longer sup
OK, let's reset. We are discussing dynamically created bag indexes to
hold indexing requests for types without a covering index. In your
problem scenario above:
-TypeSystem: t2 and t3 derive from t1
-User defined sorted index exists for t3
-fs of type t2 added to index -> causes bag index for t2
On 2/7/07, Lev Kozakov <[EMAIL PROTECTED]> wrote:
This exception is never thrown in our test cases, because we don't use URLs
containing wrong descriptor XML files. We encountered this problem in the
OSGi context, and I decided to fix it in all releases of the code.
Can we add a test case for
So what if t3 has a user defined index, e.g., a sorted index? Then the
bag index for t1 must make sure not to mention t3 at all.
Eddie Epstein wrote:
Assuming t3 is also derived from t1, and t3 already has a bag index
defined, couldn't the t1 bag index link to the existing bag index for
t3 ins
On 2/8/07, Eddie Epstein <[EMAIL PROTECTED]> wrote:
Would another alternative be: when t2 is indexed, create the bag index
for t1 (assuming t1 is derived from TOP, else t1's parent directly
derived from TOP)?
This seems about equivalent to Thilo's proposal, except it does not
handle the case w
Assuming t3 is also derived from t1, and t3 already has a bag index
defined, couldn't the t1 bag index link to the existing bag index for
t3 instead of creating a new one?
No. t1 may have other subtypes which already have indexes.
Eddie Epstein wrote:
Would another alternative be: when t2 is indexed, create the bag index
for t1 (assuming t1 is derived from TOP, else t1's parent directly
derived from TOP)?
Eddie
On 2/8/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
Would another alternative be: when t2 is indexed, create the bag index
for t1 (assuming t1 is derived from TOP, else t1's parent directly
derived from TOP)?
Eddie
On 2/8/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
I guess I didn't really pay proper attention when I reviewed this
earlier. While
[
https://issues.apache.org/jira/browse/UIMA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471291
]
Marshall Schor commented on UIMA-284:
-
A (partial) list of things being investigated and corrected:
In several pla
Michael notes an even more serious problem. When you later try to
retrieve all FSs of type t2, it is arbitrary what index is used: the one
created for t2, or the one for t1. If the one for t1 is used, not all
FSs of type t2 will be returned, as at least one was added to the t2
index before th
I guess I didn't really pay proper attention when I reviewed this
earlier. While going over the CAS documentation, a couple of (related)
issues became apparent that I hadn't noticed before, and that we should
fix before we release. Both issues have to do with inheritance.
Suppose you have tw
[
https://issues.apache.org/jira/browse/UIMA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-291.
-
Resolution: Fixed
fixed script files. Add svn property svn:eol-style=LF for all *.sh script files
"bad interpreter" when using pearMerger.sh script on linux
---
Key: UIMA-291
URL: https://issues.apache.org/jira/browse/UIMA-291
Project: UIMA
Issue Type: Bug
Components: Bui
50 matches
Mail list logo
