[
https://issues.apache.org/jira/browse/UIMA-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-209:
Attachment: fsEqualsTest.patch
FeatureStructure.equals returns false for same FS obtained through different
[
https://issues.apache.org/jira/browse/UIMA-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-180.
-
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
After adding the section on migrating
Components: Tools
Reporter: Adam Lally
Assigned To: Adam Lally
Priority: Minor
Fix For: 2.1
Change to uimaj-tools/src/main/javajet/jcasgen because:
(1) maven convention is to have the directory immediatley under main indicate
the kind of file
[
https://issues.apache.org/jira/browse/UIMA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-211.
---
Resolution: Fixed
Restructure directory uimaj-tools/src/main/org.apache.uima.jcasgen
On 1/17/07, Marshall Schor [EMAIL PROTECTED] wrote:
I don't think you need to remove catch blocks from user code. If the
try/catch
is left in, then the user would get the warning that we're getting.
No, this is a different situation.
void someMethod() throw SomeException {
//Not a compile
[
https://issues.apache.org/jira/browse/UIMA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-10.
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
Refactoring complete. Assigning
[
https://issues.apache.org/jira/browse/UIMA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-84:
Assignee: Marshall Schor
Mirko was able to reproduce the issue.
CDE's Find AE Dialog does not work
Issue Type: Bug
Components: Core Java Framework
Environment: Sun Java 1.5
Reporter: Adam Lally
Assigned To: Adam Lally
Fix For: 2.1
JMX MBean registration fails, logging a warning message, if an AE name
contains a comma or other
[
https://issues.apache.org/jira/browse/UIMA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-199.
---
Resolution: Fixed
JMX Support has problems with AE names containing special characters (e.g.
commas
: Core Java Framework
Reporter: Adam Lally
Assigned To: Adam Lally
Priority: Minor
Fix For: 2.1
Careful checking of the log file for AnalysisEngine_implTest shows that there
are CAS returned to pool from which it was not checked out warnings
On 1/17/07, Lev Kozakov [EMAIL PROTECTED] wrote:
I agree - documenting the limitation and workaround (using Xerces) is a good
idea.
I'll open a JIRA issue to update the documentation.
The 'isValidXmlFile' is used in PEAR installation to make sure the XML file
that requires
[
https://issues.apache.org/jira/browse/UIMA-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-200.
---
Resolution: Fixed
Excessive releases of CAS on error in Aggregate CasMultiplier
Components: Documentation
Reporter: Adam Lally
Priority: Minor
When Sun Java 1.4, the XML parser bundled with the JRE does not support:
* Schema validation
* Parsing of XML descriptors containing a Byte Order Mark
This can be addressed by installing Xerces, or using a different JRE
On 1/17/07, Marshall Schor [EMAIL PROTECTED] wrote:
Somethings is likely amiss - any ideas?
Other data points:
When running this as part of mvn install - the test on the mac takes 57
seconds (pretty consistent)
When running this from eclipse, as a single test, on the mac, this takes
21
[
https://issues.apache.org/jira/browse/UIMA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465586
]
Adam Lally commented on UIMA-198:
-
This is due to Maven bug http://jira.codehaus.org/browse/MSUREFIRE-148, which
has
[
https://issues.apache.org/jira/browse/UIMA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-202.
-
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally
[
https://issues.apache.org/jira/browse/UIMA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-45.
--
Resolution: Fixed
Significant cleanup has been done. Further items can be opened under separate
JIRA issues
[
https://issues.apache.org/jira/browse/UIMA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-10:
Eliminate static methods on JCasImpl that are called from JCas cover classes.
Create JCasRegistry class instead
On 1/16/07, Mirko Jahn [EMAIL PROTECTED] wrote:
Thanks for the tips! That helped me to idenitfy the failing unit tests.
I now figured out that there are tests in cpm, which only fail with
mvn test
but not with
mvn install
I am able to reproduce that, on Windows even.
I'm not sure what
Reporter: Adam Lally
Priority: Minor
There are tests in cpm, which only fail with
mvn test
but not with
mvn install
Or when run from Eclipse.
The failing tests are:
org.apache.uima.collection.impl.CollectionProcessingEngine_implTest
On 1/16/07, Lev Kozakov [EMAIL PROTECTED] wrote:
The PEAR validation code uses UIMA ResourceManager mechanism to add several
JARs to the classpath, but it does not override the default class loader.
Therefore, the 'extension' classes, which are specified in the component
classpath, are searched
On 1/16/07, Lev Kozakov [EMAIL PROTECTED] wrote:
On 1/15/07, Adam Lally (JIRA) uima-dev@incubator.apache.org wrote:
PEAR Encoding Test gives NullPointerException under Sun Java 1.4.2
Yes, Sun Java 1.4.2 cannot process BOM at the beginning of XML files. The
test fails
[
https://issues.apache.org/jira/browse/UIMA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-191:
---
Assignee: Marshall Schor
CDE: adding feature value type in default namespace does not work correctly
[
https://issues.apache.org/jira/browse/UIMA-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-189 started by Adam Lally.
Maven building on *nix platforms including Mac OS X broken in several ways
[
https://issues.apache.org/jira/browse/UIMA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-188.
---
Resolution: Fixed
Fix Version/s: 2.1
Fixed by deleting the output file before running the AE
Components: Eclipse plugins
Environment: Mac OS X
Eclipse v3.2.1
Reporter: Adam Lally
Priority: Minor
On the CDE's Aggregate page, in the Find AE dialog, the use selected a
descriptor and clicked OK. The dialog closed but the selected AE was not added
[
https://issues.apache.org/jira/browse/UIMA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-188:
-
The fix causes test to fail in other circumstances. Apparently File.delete()
can't be relied upon
Components: Core Java Framework
Environment: Sun Java 1.4.2_12
Reporter: Adam Lally
java.lang.NullPointerException
at
org.apache.uima.pear.util.PearEncodingTest.testUTF8WithSignature(PearEncodingTest.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0
[
https://issues.apache.org/jira/browse/UIMA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-45 started by Adam Lally.
Review and clean up unit tests
--
Key: UIMA-45
URL: https
Currently there are three static methods on JCasImpl that are called
from JCasGen-erated cover classes. I'd like to do something about
this because it means we haven't fully separated the JCas interface
and implementation. For example I could (theoretically, someday) call
new MyJCasType(jcas)
Pushed send a little too quick... I also had another point to make.
Currently getNextIndex() does something strange - it queries the
current Java stack trace to figure out which cover class called it, so
that it knows which index is assigned to which class. This was added
after-the-fact so as
On 1/12/07, Marshall Schor [EMAIL PROTECTED] wrote:
We're changing a reasonable amount of stuff for 2.1. I think we might
need a migration guide. This could be both a chapter in the docbooks
and also a page on our website.
Yes, definitely. I will work on this as part of
[
https://issues.apache.org/jira/browse/UIMA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-182:
-
This should be enhanced so that the framework reports which descriptor files
contain the type definitions
[
https://issues.apache.org/jira/browse/UIMA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-182.
-
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
Extend CasCreationUtils methods
Eddie, you removed the classes TCASException and TCASRuntimeException
but I see that the message digests tcas_errors.proprties and
tcas_runtime_exc.properties are still there. Do these need to be
merged with the CASException and CASRuntimeException?
-Adam
On 1/12/07, Thilo Goetz [EMAIL PROTECTED] wrote:
When I wrote that script, some tests wouldn't pass and the build
stopped. Since I was interested in building the distribution, I removed
the tests. If our tests are at a stage now where they normally pass,
let's just remove the switch.
The
/jira/browse/UIMA-186
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Reporter: Adam Lally
Assigned To: Adam Lally
Fix For: 2.1
Problem exposed by this line in AnalysisEngine_implTest, previously commented
out
[
https://issues.apache.org/jira/browse/UIMA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-186.
---
Resolution: Fixed
AnalysisEngine.setResultSpecification doesn't clear out previously cached
result
On 1/11/07, Michael Baessler [EMAIL PROTECTED] wrote:
Thilo Goetz wrote:
CAS.declareFsVariable(String name, Type type)
CAS.isFsVariable(String name):boolean
CAS.getFsVariableType(String name):Type
I would like to have an additional method like
CAS.getFsVariableForType(Type type):FS
so that
The CDE uses the UIMA Framework calls to build the merged type system;
it doesn't do any merging itself. Can the Framework code pass back
value somehow indicating if feature-extension style of merging happened?
If so, this could probably get into 2.1.
Yes, I could add a new variant of
On 1/11/07, Eddie Epstein [EMAIL PROTECTED] wrote:
Having not heard a user request for global variables, I'm a little
fuzzy on the use case.
I think one use case is the singleton use case. You could define a
global variable called myapp.documentMetadata and set its value to
an instance of
[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463937
]
Adam Lally commented on UIMA-125:
-
The error is because in your type system, type TTAnnotation explicitly defnies
[
https://issues.apache.org/jira/browse/UIMA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-170.
-
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
Marshall, please review my
FYI a while back a user reported an issue with the DocumentAnalyzer
that it always truncates long string values and provides no way to
view them:
https://issues.apache.org/jira/browse/UIMA-38
So it seems like after this fix the CVD may now have that same issue.state.
-Adam
On 1/11/07, Thilo
On 1/11/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I hear you ;-) Maybe I could provide a pop-up that lets one view the
whole string in a separate window if desired.
I think that would address the issue. It's not critical for 2.1, but
maybe just add a comment to UIMA-38 to remind us to do it
On 1/11/07, Marshall Schor [EMAIL PROTECTED] wrote:
The CDE actually does two different calls to build merged type systems,
depending on
whether or not it's editing an aggregate.
If it's an aggregate, it calls:
CasCreationUtils.mergeDelegateAnalysisEngineTypeSystems
If it's not, it calls:
://issues.apache.org/jira/browse/UIMA-182
Project: UIMA
Issue Type: Sub-task
Components: Core Java Framework
Reporter: Adam Lally
Assigned To: Adam Lally
Fix For: 2.1
--
This message is automatically generated by JIRA.
-
If you think
[
https://issues.apache.org/jira/browse/UIMA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-182.
---
Resolution: Fixed
Extend CasCreationUtils methods for type system merging to return list of
types where
[
https://issues.apache.org/jira/browse/UIMA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-177:
Fix Version/s: 2.1
Base framework support for this has been implemented in UIMA-182 subtask.
Changed fix
[
https://issues.apache.org/jira/browse/UIMA-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-173.
-
Resolution: Fixed
Assignee: Thilo Goetz (was: Adam Lally)
Work complete and documented updated
[
https://issues.apache.org/jira/browse/UIMA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-165.
-
Resolution: Fixed
Need JCAS fixes for DocumentatAnnotation and type merging
I was getting some unit test failures when running in Maven, but not
in Eclipse. I think the reasons are important for everyone to
understand.
In Maven, test cases are not allowed to access test classes or
resources from other projects. For example, classes in
uimaj-cpe/src/test/java cannot
[
https://issues.apache.org/jira/browse/UIMA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-143:
-
This change was undone with UIMA-168 due to a lack of consensus among the
committers.
JCas and CAS
[
https://issues.apache.org/jira/browse/UIMA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-143:
---
Assignee: (was: Adam Lally)
JCas and CAS interface and impl refactoring for more sharing
[
https://issues.apache.org/jira/browse/UIMA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-113:
---
Assignee: Eddie Epstein (was: Adam Lally)
socket timeout exception is (sometimes?) embedded in sax
[
https://issues.apache.org/jira/browse/UIMA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-157.
---
won't fix, at least not in this form
CAS / CasView API refactoring
It's time for board reports again...
-- Forwarded message --
From: Noel J. Bergman [EMAIL PROTECTED]
Date: Jan 9, 2007 8:57 AM
Subject: REMINDER January 2007 Board Reports
To: general@incubator.apache.org
This is a short reporting month, given that January 1 was a Monday, so
[
https://issues.apache.org/jira/browse/UIMA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-15:
--
Assignee: Marshall Schor
Assigning to Marshall to coordinate any necessary documentation updates
On 12/19/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I guess we want about 2 weeks of testing, doc review etc. before that.
So this would mean we enter the test phase around the middle of January.
So here's a tentative schedule:
now - 1/21/07:coding, general enhancements
1/22/07 - 2/4/07:
[
https://issues.apache.org/jira/browse/UIMA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-169.
---
Resolution: Fixed
Create separate uima-document-annotation Maven project and jar file
[
https://issues.apache.org/jira/browse/UIMA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-167:
Fix Version/s: 2.1
Assignee: Marshall Schor
Is this done?
Find and verify Docbook license(s
[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463574
]
Adam Lally commented on UIMA-125:
-
XCAS service communication between Apache UIMA 2.1 and IBM UIMA 2.0 already
works
[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463588
]
Adam Lally commented on UIMA-125:
-
Eddie's the expert, but my understanding is that you CAN deserialize a v1.x
XCAS
A question mainly for Thilo. This is my idea for implementing the
default bag index proposal - that is, when someone calls
IndexRepository.addFS(fs) when there are no indexes defined over the
type of the fs, a bag index will be created:
public void ll_addFS(int fsRef) {
// Determine type
I stumbled across this:
private void incrementIllegalIndexUpdateDetector(int typeCode) {
this.detectIllegalIndexUpdates[typeCode] =
(this.detectIllegalIndexUpdates[typeCode] == Integer.MAX_VALUE) ?
Integer.MIN_VALUE
: this.detectIllegalIndexUpdates[typeCode] + 1;
}
I think this
[
https://issues.apache.org/jira/browse/UIMA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-164.
-
Resolution: Fixed
Assignee: Thilo Goetz (was: Adam Lally)
Assigning to our release manager
We should review the warnings that our javadoc build produces. This is issue
https://issues.apache.org/jira/browse/UIMA-70. It's currently
assigned to me but anybody is welcome to reassign it to themselves and
work on it.
-Adam
[
https://issues.apache.org/jira/browse/UIMA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-104.
-
Resolution: Fixed
Assignee: Michael Baessler (was: Adam Lally)
Applied edits as suggested by Lev
[
https://issues.apache.org/jira/browse/UIMA-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-173 started by Adam Lally.
Create Default Bag Indexes when addFsToIndexes is called but no index has
been defined for that type
Components: Core Java Framework
Reporter: Adam Lally
Assigned To: Marshall Schor
In light of the issues with composability of annotators that use JCas combined
with type merging (using different definitions of the same type, with
different feature sets), we should add a notification
On 1/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: twgoetz
Date: Tue Jan 9 06:00:11 2007
New Revision: 494413
URL: http://svn.apache.org/viewvc?view=revrev=494413
Log:
Jira UIMA-25: remove strange array type subsumption code.
https://issues.apache.org/jira/browse/UIMA-25
snip/
On 1/9/07, Eddie Epstein [EMAIL PROTECTED] wrote:
There seems to be agreement in the behavior, just a problem with naming?
Why can't the object delivered to analytics be called a CAS, and CasView
be derived from CAS? Backward compatibility will required a migration step
that renames the local
On 1/9/07, Marshall Schor [EMAIL PROTECTED] wrote:
An interesting idea. It would seem quite possible to set up JCas so
that the Java cover objects would be specific for each component, reused
within that component, but dropped when the component exited. This
would allow different definitions
On 1/9/07, Eddie Epstein [EMAIL PROTECTED] wrote:
On 1/9/07, Thilo Goetz [EMAIL PROTECTED] wrote:
a) backward compatibility and b) some people actually seem to be using
it and don't want to be without it.
Then perhaps OSGi components will not be compatible with distributed
definitions,
but
[
https://issues.apache.org/jira/browse/UIMA-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-116.
-
Resolution: Won't Fix
Fix Version/s: (was: 2.1)
No consensus that this should be done
On 1/9/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I have no problem with that, but it's disappointing. Can you give me
some insight into what the problems are exactly? In a few lines? Thanks.
I think the main problem is that the UIMA framework OSGi bundle has to
load the JCas cover classes
Note I already commented on this, by replying to the commit message
(which goes to uima-dev). I haven't gotten a response... did that get
caught by some filter?
-Adam
On 1/9/07, Marshall Schor [EMAIL PROTECTED] wrote:
Thilo Goetz (JIRA) wrote:
[
On 1/9/07, Marshall Schor [EMAIL PROTECTED] wrote:
Being that we're copying what other Apache projects do here with regard
to 3rd party JARs, I don't think we have to
be concerned, beyond what the README-FIRST does.
Where exactly did you get this stuff from? I got a nightly Velocity
snapshot
On 1/9/07, Marshall Schor [EMAIL PROTECTED] wrote:
This is not on our code conventions page, but I'd like to put it there.
I think we discussed this a long time ago - and found the apache way
was more to honor the community, rather than call out specific authors
of files. For those who wish
Components: Core Java Framework
Reporter: Adam Lally
Assigned To: Adam Lally
Fix For: 2.1
This is needed because the DocumentAnnotation class cannot reside in
uima-core.jar if users are going to generate their own version of it.
--
This message
On 1/7/07, Marshall Schor [EMAIL PROTECTED] wrote:
Perhaps a useful thing to explore is to consider merging *all* the
user-facing CAS APIs (CAS, CASView, JCas, JCasView), thereby
*eliminating* some APIs. I'm thinking we would still have the ability
to have multiple views, each having a
On 1/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I see two reasonable alternatives. Neither involves a CommonCas.
a) The JCas assumes its wrapper nature. It implements its additional
functionality, and for all base functions, users refer to the CAS.
b) The JCas extends the CAS. For
On 1/6/07, Thilo Goetz [EMAIL PROTECTED] wrote:
As I see it, we're not going to reach consensus on this issue. I guess
this is at least in part due to the fact that we disagree on the basic
premises underlying this redesign. I am -1 to the current proposal, and
I'll give my reasons below.
Even if we don't do the larger view redesign, I still think it makes
sense to drop TCAS:
http://issues.apache.org/jira/browse/UIMA-115
There is little reason for TCAS to still exist at this point - it no
longer defines any methods that are not on CAS, and the methods
CAS.getTCAS() and
[
https://issues.apache.org/jira/browse/UIMA-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-70:
--
Assignee: Adam Lally
JavaDoc doesn't match impl
--
Key: UIMA
[
https://issues.apache.org/jira/browse/UIMA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-22:
--
Assignee: Marshall Schor
Tools still use IBM splashscreen
[
https://issues.apache.org/jira/browse/UIMA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-164:
Fix Version/s: 2.1
Add source distribution
---
Key: UIMA-164
Issue Type: Sub-task
Components: Core Java Framework
Reporter: Adam Lally
Assigned To: Marshall Schor
Fix For: 2.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators
This has been stewing for a long time, so it's time to get it out in
the open here.
Users have difficulty figuring out how to use FeatureStructures that
are not derived from annotations (and not intended to just be
subordinate objects referenced from annotations). I have personally
had to help
[
https://issues.apache.org/jira/browse/UIMA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-164:
---
Assignee: Adam Lally
Add source distribution
---
Key: UIMA-164
On 1/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
By all means, though I would like to understand what the issue is we're
addressing here. Is the concept so difficult/outlandish? Is the
documentation so bad? Are the users so slow? What is it that makes
this so difficult?
It's probably a
Also... is uima-docbooks/Source_UIMA_SDK_Guide_Ref needed for anything
or should we delete it from SVN?
-Adam
On 1/8/07, Marshall Schor [EMAIL PROTECTED] wrote:
Here's a short proposal / straw-person that might address many of the
concerns raised.
1) Drop the JCas interface - only have the CAS interface. (one less
interface; process(...) method doesn't need variants depending on kind
of API interface
On 1/8/07, Marshall Schor [EMAIL PROTECTED] wrote:
Does that mean it's OK to have these jars in SVN and in the source
distribution?
Yes. They need to be called out in the Notices file.
The site http://people.apache.org/~cliffs/3party.html has specific
instructions for
Mozilla Public License
On 1/4/07, Marshall Schor [EMAIL PROTECTED] wrote:
Adam Lally wrote:
So I think we need to deprecate addToIndexes().
Not sure about this - because the current view mechanism would
seem to make this work, even for multi-sofa. We could even put in
code that checked if the item being indexed
On 1/5/07, Thilo Goetz [EMAIL PROTECTED] wrote:
All, I have added README, NOTICE etc. to the distribution. While doing
this, I noticed that we have the logger config files
(FileConsoleLogger.properties and Logger.properties) living in the root
directory of the distribution. That's not nice. I
: https://issues.apache.org/jira/browse/UIMA-162
Project: UIMA
Issue Type: Sub-task
Components: Tools
Reporter: Adam Lally
Assigned To: Adam Lally
Priority: Minor
Fix For: 2.1
--
This message is automatically generated
On 1/5/07, Marshall Schor [EMAIL PROTECTED] wrote:
After thinking harder about this - I'm concluding that users will need
to run a migration tool in any case to convert old JCas source classes
to the Apache form, and that tool can just as well do a conversion of
the previous 2 source class
[
https://issues.apache.org/jira/browse/UIMA-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-163.
---
Resolution: Fixed
CpeCasProcessors.removeCasProcessor always throws invalid index exception
On 1/5/07, Marshall Schor [EMAIL PROTECTED] wrote:
After thinking harder about this - I'm concluding that users will need
to run a migration tool in any case to convert old JCas source classes
to the Apache form, and that tool can just as well do a conversion of
the previous 2 source class
701 - 800 of 1020 matches
Mail list logo
