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

Reply via email to