You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2009/07/28 18:12:48 UTC
next release plan - sandbox - which components?
Let's get a list of sandbox projects we plan to include in the
2.3.0-incubating release.
The reason for doing this is to better update the version info for the
sandbox. For uimaj we use maven properties and have the version info in
just one place for all the projects. We could do that too, for sandbox
projects which are in the "normal" release cycle.
Here's the current projects, and my thoughts on including in the release
(quick summary - release all except OpenCalaisAnnotatorGroovy, with some
warinings about projects which may be omitted, if not ready).
Given this, to make the release easier, I propose updating the
SandboxDistr pom to
a) include the new sandbox projects considered for the release, and
b) to define the sandbox release number(s)
and then change the sandbox projects to specify this pom as their parent.
The * in the list below (of all sandbox projects) means it is included
in the sandbox distr currently as a <module>
BSFAnnotator - yes (bean scripting framework)
CasViewerEclipsePlugin - no (replaced by CasEditor)
ConceptMapper - yes (if ready by release time)(initial release)
ConfigurableFeatureExtractor - yes (if ready by release time)(initial
release)
*DictionaryAnnotator - yes
FsVariables - yes
Lucas - yes (if ready)(initial release)
OpenCalaisAnnotator - yes
OpenCalaisAnnotatorGroovy - no (not updated to work with current Calais
levels)
*PearPackagingAntTask - yes
*PearPackagingMavenPlugin - yes
*RegularExpressionAnnotator -yes
SandboxDistr - yes (shared info used by other projects)
SandboxDocs - yes (shared info used by docbooks)
*SimpleServer - yes
SimpleUimaAsService - yes
SnowballAnnotator - yes
*Tagger - yes (this is the hidden markov model tagger)
TikaAnnotator - yes
uima-as - yes
*WhiteSpaceTokenizer - yes
Currently some of the sandbox projects (e.g. PearPackagingMavenPlug)
have not had their version numbers updated - and I could either update
them to a specific version number (e.g. 2.3.0-incubating-SNAPSHOT) or
use the convention we have for uimaj where we set these to a ${property}
and share the update of that in the SandboxDistr.
Doing this would make the sandbox builds more like the main one, and
consolidate the places where we need to change version numbers.
Opinions?
-Marshall
Re: next release plan - sandbox - which components?
Posted by Marshall Schor <ms...@schor.com>.
Marshall Schor wrote:
> Let's get a list of sandbox projects we plan to include in the
> 2.3.0-incubating release.
>
> The reason for doing this is to better update the version info for the
> sandbox. For uimaj we use maven properties and have the version info in
> just one place for all the projects. We could do that too, for sandbox
> projects which are in the "normal" release cycle.
>
> Here's the current projects, and my thoughts on including in the release
> (quick summary - release all except OpenCalaisAnnotatorGroovy, with some
> warinings about projects which may be omitted, if not ready).
>
> Given this, to make the release easier, I propose updating the
> SandboxDistr pom to
> a) include the new sandbox projects considered for the release, and
>
Excepting uima-as which has its own separate build, and is not itself a
project but a set of projects
-Marshall
> b) to define the sandbox release number(s)
>
> and then change the sandbox projects to specify this pom as their parent.
>
> The * in the list below (of all sandbox projects) means it is included
> in the sandbox distr currently as a <module>
>
> BSFAnnotator - yes (bean scripting framework)
> CasViewerEclipsePlugin - no (replaced by CasEditor)
> ConceptMapper - yes (if ready by release time)(initial release)
> ConfigurableFeatureExtractor - yes (if ready by release time)(initial
> release)
> *DictionaryAnnotator - yes
> FsVariables - yes
> Lucas - yes (if ready)(initial release)
> OpenCalaisAnnotator - yes
> OpenCalaisAnnotatorGroovy - no (not updated to work with current Calais
> levels)
> *PearPackagingAntTask - yes
> *PearPackagingMavenPlugin - yes
> *RegularExpressionAnnotator -yes
> SandboxDistr - yes (shared info used by other projects)
> SandboxDocs - yes (shared info used by docbooks)
> *SimpleServer - yes
> SimpleUimaAsService - yes
> SnowballAnnotator - yes
> *Tagger - yes (this is the hidden markov model tagger)
> TikaAnnotator - yes
> uima-as - yes
> *WhiteSpaceTokenizer - yes
>
> Currently some of the sandbox projects (e.g. PearPackagingMavenPlug)
> have not had their version numbers updated - and I could either update
> them to a specific version number (e.g. 2.3.0-incubating-SNAPSHOT) or
> use the convention we have for uimaj where we set these to a ${property}
> and share the update of that in the SandboxDistr.
>
> Doing this would make the sandbox builds more like the main one, and
> consolidate the places where we need to change version numbers.
>
> Opinions?
>
> -Marshall
>
>
>
Re: next release plan - sandbox - which components?
Posted by Marshall Schor <ms...@schor.com>.
Hi Rico - thanks for the reminder :-) I'll add it... -Marshall
Rico Landefeld wrote:
> hi there,
>
> Lucas should be part of the upcomming 2.3.0 release.
>
> rico
>
>
> On Thu, Jul 30, 2009 at 12:56 AM, Tong Fin<to...@gmail.com> wrote:
>
>>>> Is the SimpleUimaAsService ready for prime time? I don't
>>>> recall what it was, but I was looking at it the other day
>>>> and thought it didn't look quite ready yet. Maybe I'm
>>>> mistaken. For example, it has the SimpleServer jars
>>>> checked in as binaries. We surely don't want that, so
>>>> at least the build ought to be fixed. The rest works,
>>>> I assume? Is it documented? Anybody using it?
>>>>
>>>>
>>> I think it has some use. Tong?
>>> Thilo - can you please post as many specifics on things that need fixing
>>> here or maybe even open Jira issues?
>>>
>> I think there are more works to be done for SimpleUimaAsService like JUnit
>> testing and documentation.
>> I prefer to not include SimpleUimaAsService for this next release unless we
>> have users for this project (currently, there is no user (yet) from what I
>> know).
>>
>> -- Tong
>>
>>
>
>
>
Re: next release plan - sandbox - which components?
Posted by Rico Landefeld <ri...@googlemail.com>.
hi there,
Lucas should be part of the upcomming 2.3.0 release.
rico
On Thu, Jul 30, 2009 at 12:56 AM, Tong Fin<to...@gmail.com> wrote:
>> > Is the SimpleUimaAsService ready for prime time? I don't
>> > recall what it was, but I was looking at it the other day
>> > and thought it didn't look quite ready yet. Maybe I'm
>> > mistaken. For example, it has the SimpleServer jars
>> > checked in as binaries. We surely don't want that, so
>> > at least the build ought to be fixed. The rest works,
>> > I assume? Is it documented? Anybody using it?
>> >
>>
>> I think it has some use. Tong?
>> Thilo - can you please post as many specifics on things that need fixing
>> here or maybe even open Jira issues?
>
>
> I think there are more works to be done for SimpleUimaAsService like JUnit
> testing and documentation.
> I prefer to not include SimpleUimaAsService for this next release unless we
> have users for this project (currently, there is no user (yet) from what I
> know).
>
> -- Tong
>
Re: next release plan - sandbox - which components?
Posted by Tong Fin <to...@gmail.com>.
> > Is the SimpleUimaAsService ready for prime time? I don't
> > recall what it was, but I was looking at it the other day
> > and thought it didn't look quite ready yet. Maybe I'm
> > mistaken. For example, it has the SimpleServer jars
> > checked in as binaries. We surely don't want that, so
> > at least the build ought to be fixed. The rest works,
> > I assume? Is it documented? Anybody using it?
> >
>
> I think it has some use. Tong?
> Thilo - can you please post as many specifics on things that need fixing
> here or maybe even open Jira issues?
I think there are more works to be done for SimpleUimaAsService like JUnit
testing and documentation.
I prefer to not include SimpleUimaAsService for this next release unless we
have users for this project (currently, there is no user (yet) from what I
know).
-- Tong
Re: next release plan - sandbox - which components?
Posted by Marshall Schor <ms...@schor.com>.
Thilo Goetz wrote:
> Marshall Schor wrote:
>
>> Let's get a list of sandbox projects we plan to include in the
>> 2.3.0-incubating release.
>>
>> The reason for doing this is to better update the version info for the
>> sandbox. For uimaj we use maven properties and have the version info in
>> just one place for all the projects. We could do that too, for sandbox
>> projects which are in the "normal" release cycle.
>>
>> Here's the current projects, and my thoughts on including in the release
>> (quick summary - release all except OpenCalaisAnnotatorGroovy, with some
>> warinings about projects which may be omitted, if not ready).
>>
>> Given this, to make the release easier, I propose updating the
>> SandboxDistr pom to
>> a) include the new sandbox projects considered for the release, and
>> b) to define the sandbox release number(s)
>>
>> and then change the sandbox projects to specify this pom as their parent.
>>
>> The * in the list below (of all sandbox projects) means it is included
>> in the sandbox distr currently as a <module>
>>
>> BSFAnnotator - yes (bean scripting framework)
>> CasViewerEclipsePlugin - no (replaced by CasEditor)
>> ConceptMapper - yes (if ready by release time)(initial release)
>> ConfigurableFeatureExtractor - yes (if ready by release time)(initial
>> release)
>> *DictionaryAnnotator - yes
>> FsVariables - yes
>> Lucas - yes (if ready)(initial release)
>> OpenCalaisAnnotator - yes
>> OpenCalaisAnnotatorGroovy - no (not updated to work with current Calais
>> levels)
>> *PearPackagingAntTask - yes
>> *PearPackagingMavenPlugin - yes
>>
>
> Are you going to move the PearPackagingMavenPlugin to the core?
> There was agreement that we should do so:
> http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg09655.html
>
OK - missed that one. I'll move it to the core.
>
>> *RegularExpressionAnnotator -yes
>> SandboxDistr - yes (shared info used by other projects)
>> SandboxDocs - yes (shared info used by docbooks)
>> *SimpleServer - yes
>> SimpleUimaAsService - yes
>>
>
> Is the SimpleUimaAsService ready for prime time? I don't
> recall what it was, but I was looking at it the other day
> and thought it didn't look quite ready yet. Maybe I'm
> mistaken. For example, it has the SimpleServer jars
> checked in as binaries. We surely don't want that, so
> at least the build ought to be fixed. The rest works,
> I assume? Is it documented? Anybody using it?
>
I think it has some use. Tong?
Thilo - can you please post as many specifics on things that need fixing
here or maybe even open Jira issues?
>
>> SnowballAnnotator - yes
>> *Tagger - yes (this is the hidden markov model tagger)
>> TikaAnnotator - yes
>> uima-as - yes
>> *WhiteSpaceTokenizer - yes
>>
>> Currently some of the sandbox projects (e.g. PearPackagingMavenPlug)
>> have not had their version numbers updated - and I could either update
>> them to a specific version number (e.g. 2.3.0-incubating-SNAPSHOT) or
>> use the convention we have for uimaj where we set these to a ${property}
>> and share the update of that in the SandboxDistr.
>>
>> Doing this would make the sandbox builds more like the main one, and
>> consolidate the places where we need to change version numbers.
>>
>
> Definitely +1. Anything that makes the build easier to maintain.
>
>
>> Opinions?
>>
>> -Marshall
>>
>
>
>
>
Re: next release plan - sandbox - which components?
Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Let's get a list of sandbox projects we plan to include in the
> 2.3.0-incubating release.
>
> The reason for doing this is to better update the version info for the
> sandbox. For uimaj we use maven properties and have the version info in
> just one place for all the projects. We could do that too, for sandbox
> projects which are in the "normal" release cycle.
>
> Here's the current projects, and my thoughts on including in the release
> (quick summary - release all except OpenCalaisAnnotatorGroovy, with some
> warinings about projects which may be omitted, if not ready).
>
> Given this, to make the release easier, I propose updating the
> SandboxDistr pom to
> a) include the new sandbox projects considered for the release, and
> b) to define the sandbox release number(s)
>
> and then change the sandbox projects to specify this pom as their parent.
>
> The * in the list below (of all sandbox projects) means it is included
> in the sandbox distr currently as a <module>
>
> BSFAnnotator - yes (bean scripting framework)
> CasViewerEclipsePlugin - no (replaced by CasEditor)
> ConceptMapper - yes (if ready by release time)(initial release)
> ConfigurableFeatureExtractor - yes (if ready by release time)(initial
> release)
> *DictionaryAnnotator - yes
> FsVariables - yes
> Lucas - yes (if ready)(initial release)
> OpenCalaisAnnotator - yes
> OpenCalaisAnnotatorGroovy - no (not updated to work with current Calais
> levels)
> *PearPackagingAntTask - yes
> *PearPackagingMavenPlugin - yes
Are you going to move the PearPackagingMavenPlugin to the core?
There was agreement that we should do so:
http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg09655.html
> *RegularExpressionAnnotator -yes
> SandboxDistr - yes (shared info used by other projects)
> SandboxDocs - yes (shared info used by docbooks)
> *SimpleServer - yes
> SimpleUimaAsService - yes
Is the SimpleUimaAsService ready for prime time? I don't
recall what it was, but I was looking at it the other day
and thought it didn't look quite ready yet. Maybe I'm
mistaken. For example, it has the SimpleServer jars
checked in as binaries. We surely don't want that, so
at least the build ought to be fixed. The rest works,
I assume? Is it documented? Anybody using it?
> SnowballAnnotator - yes
> *Tagger - yes (this is the hidden markov model tagger)
> TikaAnnotator - yes
> uima-as - yes
> *WhiteSpaceTokenizer - yes
>
> Currently some of the sandbox projects (e.g. PearPackagingMavenPlug)
> have not had their version numbers updated - and I could either update
> them to a specific version number (e.g. 2.3.0-incubating-SNAPSHOT) or
> use the convention we have for uimaj where we set these to a ${property}
> and share the update of that in the SandboxDistr.
>
> Doing this would make the sandbox builds more like the main one, and
> consolidate the places where we need to change version numbers.
Definitely +1. Anything that makes the build easier to maintain.
>
> Opinions?
>
> -Marshall