Mailing-List: contact ctakes-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ctakes-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of steven.bethard@colorado.edu
 designates 128.138.128.246 as permitted sender)
From: Steven Bethard <steven.bethard@Colorado.EDU>
To: "ctakes-dev@incubator.apache.org" <ctakes-dev@incubator.apache.org>
Date: Thu, 11 Oct 2012 15:57:53 -0600
Subject: Re: cTAKES uber jar distribution
Thread-Topic: cTAKES uber jar distribution
Thread-Index: Ac2n+3ceWqNLTkKHSU6S2/Sef6K3Eg==
Message-ID: <C71B3DAB-968A-46CB-AAF0-93FF316D18A3@colorado.edu>
References: 
 <B1D5DE3F00E17F458CC1B5158EA798B3018F6D@MSGPEXCEI10A.mfad.mfroot.org>
 <924DE05C19409B438EB81DE683A942D920482D@CHEXMBX1A.CHBOSTON.ORG>
 <B1D5DE3F00E17F458CC1B5158EA798B30198E0@MSGPEXCEI10A.mfad.mfroot.org>
In-Reply-To: 
 <B1D5DE3F00E17F458CC1B5158EA798B30198E0@MSGPEXCEI10A.mfad.mfroot.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Oct 11, 2012, at 3:21 PM, "Bleeker, Troy C." <Bleeker.Troy@mayo.edu> wro=
te:
> 1) A "user" (researcher but non-programmer) wants value from cTAKES with =
no compiles, no dev env, just simple download/install/use.

This sounds like someone who wants an executable jar file including all the=
 dependencies. We can create such a thing when there's a cTAKES GUI, using =
an approach like the following:

http://stackoverflow.com/questions/574594/how-can-i-create-an-executable-ja=
r-with-dependencies-using-maven

> 2) A programmer new to cTAKES wants to take the whole, as quickly as poss=
ible, into some kind of dev env, hopes not to have to deal with any depende=
ncy or build issues (given a stable release) and invoke the APIs. Kick the =
tires is the notion.

This sounds like someone who wants a jar file with all the dependencies, bu=
t doesn't care if it's executable.

They can use the same jar file as generated for (1).

(I personally think that any programmer who "hopes not to have to deal with=
 any dependency" is a lost cause in terms of a programmer, but it wouldn't =
cost us anything to support this use case.)

> 3) A programmer uses cTAKES mostly as a black-box. They take cTAKES as a =
whole, perhaps minimal changes, include everything. Although dictionaries c=
ould be replaced if they desire.

I'm not sure what the difference between this person and the person from (2=
) is. Do they also just want the jar files? Or do they want something else?

Here's a more concrete suggestion:

3.5) A programmer who wants to use their favorite dependency management too=
l (Maven, Ivy, SBT, Buildr, etc.) to depend on some (or all) of released ve=
rsions of cTAKES modules.

This is someone who wants one jar file per module, deployed to Maven Centra=
l (that's where all those dependency management tools look for jars). This =
is pretty much the default thing supported by the standard `mvn release:pre=
pare` and `mvn release:perform`.

> 4) An experienced cTAKES developer - mash cTAKES into any form they want,=
 change it, possibly contribute to Apache. May redistribute according to th=
e license.

This person will be working from the cTAKES repository, and I think it's ac=
ceptable to put additional constraints on them. In particular, I think we s=
hould say that we only promise support for:

* Building via Eclipse
* Building via Maven at the command line

Steve=