Re: Does the first Apache release contain the old CPM or the new JMS impl, or both

> I'm going thru the FAQs now, and there's one for how to scale out which > talks about the CPM. > > What should be our phase-in / out plan for this, in Apache? > > -Marshall > If this is version 2.1, seems wise to leave it in for now. Why announce a phase-out plan before an alternative is availab

Does the first Apache release contain the old CPM or the new JMS impl, or both

I'm going thru the FAQs now, and there's one for how to scale out which talks about the CPM. What should be our phase-in / out plan for this, in Apache? -Marshall

Re: naming releases

>Thinking about our customer base, what would be least confusing to them? I >think calling this release Apache UIMA 2.1 (Incubating) would be good >because: > >1) it signals that 2.0.x is the end of the line for that series, new >work is on Apache >2) it signals that Apache UIMA is the release th

[jira] Created: (UIMA-15) Semantic Search repackaging

Semantic Search repackaging --- Key: UIMA-15 URL: http://issues.apache.org/jira/browse/UIMA-15 Project: UIMA Issue Type: Task Components: Build, Packaging Reporter: Marshall Schor Do everything

[jira] Created: (UIMA-14) Plugin manifests still list IBM as the vendor

Plugin manifests still list IBM as the vendor - Key: UIMA-14 URL: http://issues.apache.org/jira/browse/UIMA-14 Project: UIMA Issue Type: Bug Components: Eclipse plugins Report

[jira] Created: (UIMA-13) Javadocs should be posted on the website

Javadocs should be posted on the website Key: UIMA-13 URL: http://issues.apache.org/jira/browse/UIMA-13 Project: UIMA Issue Type: Task Components: Website Reporter: Adam Lally

[jira] Resolved: (UIMA-7) Add javadocs to build

[ http://issues.apache.org/jira/browse/UIMA-7?page=all ] Adam Lally resolved UIMA-7. --- Resolution: Fixed > Add javadocs to build > - > > Key: UIMA-7 > URL: http://issues.apache.org/jira/browse/UIMA-7 >

Re: [jira] Commented: (UIMA-10) Split JCas into interface and implementation

Right you are - I misunderstood what was being proposed. I agree that splitting the JCas impl code into interface / impl would be a good idea and wouldn't impact things too much. -Marshall Adam Lally (JIRA) wrote: [ http://issues.apache.org/jira/browse/UIMA-10?page=comments#action_1244944

[jira] Commented: (UIMA-10) Split JCas into interface and implementation

[ http://issues.apache.org/jira/browse/UIMA-10?page=comments#action_12449444 ] Adam Lally commented on UIMA-10: I'm not seeing why making JCas an interface would require users to change their code. That would be the case if we changed the gener

[jira] Created: (UIMA-12) Change JCas impl to use inner classes rather than _Type style classes

Change JCas impl to use inner classes rather than _Type style classes - Key: UIMA-12 URL: http://issues.apache.org/jira/browse/UIMA-12 Project: UIMA Issue Type: Improvement

[jira] Commented: (UIMA-10) Split JCas into interface and implementation

[ http://issues.apache.org/jira/browse/UIMA-10?page=comments#action_12449437 ] Marshall Schor commented on UIMA-10: Doing this means users will no longer be able to use "new UserDefinedType(aJcas)", but will instead have to do something like

[jira] Updated: (UIMA-4) Set svn:eol-style and other flags on appropriate files

[ http://issues.apache.org/jira/browse/UIMA-4?page=all ] Marshall Schor updated UIMA-4: -- Description: Construct an appropriate shell script, and run it to check the eol-style and keyword and mime-type for files in SVN. For test files, check that eol-styl

[jira] Updated: (UIMA-10) Split JCas into interface and implementation

[ http://issues.apache.org/jira/browse/UIMA-10?page=all ] Adam Lally updated UIMA-10: --- Description: We should split the existing JCAS class into an interface org.apache.uima.jcas.JCas and its implementation org.apache.uima.jcas.impl.JCasImpl. This follows go

[jira] Created: (UIMA-11) org.apache.itu package should be renamed

org.apache.itu package should be renamed Key: UIMA-11 URL: http://issues.apache.org/jira/browse/UIMA-11 Project: UIMA Issue Type: Improvement Components: Core Java Framework Repo

[jira] Commented: (UIMA-10) Split JCas into interface and implementation

[ http://issues.apache.org/jira/browse/UIMA-10?page=comments#action_12449418 ] Thilo Goetz commented on UIMA-10: - Is that a typo, did you mean org.apache.uima.jcas.impl? > Split JCas into interface and implementation > -

[jira] Created: (UIMA-10) Split JCas into interface and implementation

Split JCas into interface and implementation Key: UIMA-10 URL: http://issues.apache.org/jira/browse/UIMA-10 Project: UIMA Issue Type: Improvement Components: Core Java Framework

Re: [jira] Created: (UIMA-4) Set svn:eol-style and other flags on appropriate files

Marshall Schor (JIRA) wrote: Set svn:eol-style and other flags on appropriate files -- Key: UIMA-4 URL: http://issues.apache.org/jira/browse/UIMA-4 Project: UIMA Issue Type: Task

[jira] Updated: (UIMA-9) Remove support for xi:include

[ http://issues.apache.org/jira/browse/UIMA-9?page=all ] Adam Lally updated UIMA-9: -- Priority: Minor (was: Major) > Remove support for xi:include > - > > Key: UIMA-9 > URL: http://issues.apache.org/ji

[jira] Created: (UIMA-9) Remove support for xi:include

Remove support for xi:include - Key: UIMA-9 URL: http://issues.apache.org/jira/browse/UIMA-9 Project: UIMA Issue Type: Improvement Components: Core Java Framework Reporter: Adam Lally

[jira] Created: (UIMA-7) Add javadocs to build

Add javadocs to build - Key: UIMA-7 URL: http://issues.apache.org/jira/browse/UIMA-7 Project: UIMA Issue Type: Task Components: Build, Packaging Reporter: Adam Lally Assigned To: Adam Lally

[jira] Assigned: (UIMA-8) Add examples to assembly

[ http://issues.apache.org/jira/browse/UIMA-8?page=all ] Adam Lally reassigned UIMA-8: - Assignee: Adam Lally > Add examples to assembly > > > Key: UIMA-8 > URL: http://issues.apache.org/jira/browse/UIM

[jira] Created: (UIMA-8) Add examples to assembly

Add examples to assembly Key: UIMA-8 URL: http://issues.apache.org/jira/browse/UIMA-8 Project: UIMA Issue Type: Task Components: Build, Packaging Reporter: Adam Lally The example source code,

[jira] Created: (UIMA-6) Include documentation in assembly

Include documentation in assembly - Key: UIMA-6 URL: http://issues.apache.org/jira/browse/UIMA-6 Project: UIMA Issue Type: Task Components: Build, Packaging Reporter: Adam Lally Our bui

[jira] Assigned: (UIMA-6) Include documentation in assembly

[ http://issues.apache.org/jira/browse/UIMA-6?page=all ] Adam Lally reassigned UIMA-6: - Assignee: Adam Lally > Include documentation in assembly > - > > Key: UIMA-6 > URL: http://issues.apache.o

[jira] Assigned: (UIMA-5) re-organize docbook project and update ant build scripts

[ http://issues.apache.org/jira/browse/UIMA-5?page=all ] Marshall Schor reassigned UIMA-5: - Assignee: Marshall Schor > re-organize docbook project and update ant build scripts > > >

[jira] Created: (UIMA-5) re-organize docbook project and update ant build scripts

re-organize docbook project and update ant build scripts Key: UIMA-5 URL: http://issues.apache.org/jira/browse/UIMA-5 Project: UIMA Issue Type: Task Components: Documentation

[jira] Created: (UIMA-4) Set svn:eol-style and other flags on appropriate files

Set svn:eol-style and other flags on appropriate files -- Key: UIMA-4 URL: http://issues.apache.org/jira/browse/UIMA-4 Project: UIMA Issue Type: Task Reporter: Marshall Schor

[jira] Created: (UIMA-3) Split big book into 4, rewrite to be appropriate for Apache UIMA, redo in DocBook, get it generate high-quality PDF

Split big book into 4, rewrite to be appropriate for Apache UIMA, redo in DocBook, get it generate high-quality PDF --- Key: UIMA-3 URL: http://issues.

[jira] Created: (UIMA-2) Fix licensing issues with Eclipse plugins

Fix licensing issues with Eclipse plugins - Key: UIMA-2 URL: http://issues.apache.org/jira/browse/UIMA-2 Project: UIMA Issue Type: Task Components: Eclipse plugins Reporter: Marsh

Re: line ends, Windows, SVN and Eclipse

Marshall Schor wrote: ... How about making .txt files that should be treated as test-case-input have some distinguishing type extension? That way, we could make use of subversion configuration settings, as well as have shell scripts that we could run occasionally to fix things, based on the ext

Re: naming releases

Thinking about our customer base, what would be least confusing to them? I think calling this release Apache UIMA 2.1 (Incubating) would be good because: 1) it signals that 2.0.x is the end of the line for that series, new work is on Apache 2) it signals that Apache UIMA is the release that

Re: line ends, Windows, SVN and Eclipse

Thilo Goetz wrote: We need to be careful and selective when setting this property. It's ok for source code, but anything else, we need to check. For example, we've had endless trouble with text files that we use as test case input. If eol-style is set to native on those, test cases behave d

Re: naming releases

Adam Lally wrote: Now see, if we had just changed the name of the project then we could have reset our version number to 1.0 without any problem. :) Now all options seem flawed: If we call it 2.1, it seems strange to me that 2.x would be split with 2.0 being com.ibm and 2.1 being org.apache. On

Re: naming releases

On 11/13/06, Thilo Goetz <[EMAIL PROTECTED]> wrote: Our version is currently called 1.0-SNAPSHOT, which is the Maven default. What are we going to call this version, anyway? We have 2.0 out already, and the move to Apache justifies a major version hike, to my mind. 3.0, anyone? Or are we star

Website update

I did the SVN reorganization to move uima-website under site/trunk, and I checked out the generated html files to people.apache.org. So the new website (including my instructions on how to build UIMA) should be live in a few hours. If you have uima-website checked out, please delete it and check

[jira] Resolved: (UIMA-1) Reorganize SVN

[ http://issues.apache.org/jira/browse/UIMA-1?page=all ] Adam Lally resolved UIMA-1. --- Resolution: Fixed Moved uima-website directory and deleted the obsolete site-publish directory. SVN organization is now: site/ trunk/ uima-website/ ** xml sources

Re: line ends, Windows, SVN and Eclipse

Marshall Schor wrote: ... To do this, we need to always set svn:eol-style native on all the files that might be checked out and edited. We need to be careful and selective when setting this property. It's ok for source code, but anything else, we need to check. For example, we've had endles

Re: naming releases

Marshall Schor wrote: There's a discussion on [EMAIL PROTECTED] about how to name releases when using Maven, that includes the word "incubator" / "incubating". Adam - if our releases aren't this way already, could you open an Jira issue and fix? -Marshall Our version is currently called 1.

Re: methodology for updating the web-site for a project

Marshall Schor wrote: ... It seems to me to be a bad practice to put generated files into SVN, ... One argument in favor or checking in the website is that in case of a move or crash, it's very easy to restore the web site (even for someone not at all associated with our project). Another