Adam Lally wrote:
On 1/5/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Adam Lally wrote:
> Another thought... can we continue to support the existing source
> classes with their separate _Type source files, while changing JCasGen
> to generate only one source file from now on?
Yes, but why? If
On 1/5/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Adam Lally wrote:
> Another thought... can we continue to support the existing source
> classes with their separate _Type source files, while changing JCasGen
> to generate only one source file from now on?
Yes, but why? If the user has to co
Adam Lally wrote:
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 pr
FYI, more Wiki updates:
* Added FS-creation convenience methods to CasView, with a note
that this is still under debate. However this seems to be the majority
view so I thought it was appropriate to add it.
* Added a section on what to do with the JCasGen-erated cover
classes. This is also
[
https://issues.apache.org/jira/browse/UIMA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-138.
---
Resolution: Fixed
> Example MeetingFinderCPE_withXmlDetagging.xml doesn't work
> --
[
https://issues.apache.org/jira/browse/UIMA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-162.
---
Resolution: Fixed
> Modify CPE GUI to preserve settings in CPE descriptor that's opened, even if
> GUI doesn't
On 1/5/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Solution 1:
How about always passing in a JCasView object? For unaware components,
this would be the view to use. For view aware components, this would be
some view (perhaps picked in a similar way), but the user code would be
expected to us
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 cla
[
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 form
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 format to the new single source format.
Anyone see any
CpeCasProcessors.removeCasProcessor always throws "invalid index" exception
---
Key: UIMA-163
URL: https://issues.apache.org/jira/browse/UIMA-163
Project: UIMA
Issue Typ
Adam Lally wrote:
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
[
https://issues.apache.org/jira/browse/UIMA-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462533
]
Thilo Goetz commented on UIMA-159:
--
I've added NOTICE, README etc. Will also use this issue to work on jar
manifest
[
https://issues.apache.org/jira/browse/UIMA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-160.
Resolution: Fixed
Moved properties files to config directory, updated scripts, launch
configurations and doc
Modify CPE GUI to preserve settings in CPE descriptor that's opened, even if
GUI doesn't support editing those settings
---
Key: UIMA-162
URL: http
adding documentation for PEAR API
-
Key: UIMA-161
URL: https://issues.apache.org/jira/browse/UIMA-161
Project: UIMA
Issue Type: Improvement
Components: Documentation
Affects Versions: 2.1
Logger properties files live in root directory of distribution
--
Key: UIMA-160
URL: https://issues.apache.org/jira/browse/UIMA-160
Project: UIMA
Issue Type: Improvement
C
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.
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 would like to move
them to a subdirectory call
Testing if this message is rejected.
Add license/notices etc. files for distribution
---
Key: UIMA-159
URL: https://issues.apache.org/jira/browse/UIMA-159
Project: UIMA
Issue Type: Task
Components: Build, Packaging and Test
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
>> Single-sofa code could be made to work using the same "current view"
>> idea already discussed. But multi-sofa code will have a problem.
>>
>> 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 mu
runAE utility does not identify bad XCAS input files
Key: UIMA-158
URL: https://issues.apache.org/jira/browse/UIMA-158
Project: UIMA
Issue Type: Bug
Components: Core Java Framewo
Found the problem, looks like unintentional corruption of build file
through automatic formatting.
Thilo Goetz wrote:
I have problems with various tools (WinZip, Total Commander) trying to
unpack our distribution archives (on windows). When it works, in
addition to an apache-uima folder, I ge
[
https://issues.apache.org/jira/browse/UIMA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462477
]
Michael Baessler commented on UIMA-151:
---
Thanks for looking into that topic.
I know the ICU and the BreakIterato
I have problems with various tools (WinZip, Total Commander) trying to
unpack our distribution archives (on windows). When it works, in
addition to an apache-uima folder, I get an apache-uima_ folder. I'm
still investigating, but if somebody has any insights into this issue,
let me know.
--
Jörn Kottmann wrote:
We will sign it next week, our CTO is currently on vacation.
OK. Please post when you send it in. Thanks! -Marshall
Marshall Schor wrote:
And I guess this project needs a "NOTICES" file, documenting all of
these issues.
I added a NOTICE.txt file with all the information I think is necessary.
Feel free to edit if you think something is missing.
-- Michael
30 matches
Mail list logo
