Note: Just in case you're curious, was actually planning to use Maven's plugin (Shade and Release) to assist in building and releasing...
In case you're interested, feel free to them check out: http://maven.apache.org/plugins/index.html -----Original Message----- From: Chen, Pei [mailto:[email protected]] Sent: Thursday, August 23, 2012 5:02 PM To: [email protected] Subject: RE: cTAKES 2.6 - packaging of deliverable - was RE: [jira] [Closed] (CTAKES-34) icTAKES.jar is missing from the .gz distributions Ditto +1 on separate jars, But, I actually don't think there is any contention here. I believe this was an old SF ticket that was left behind. Since, icTAKES.tar.gz doesn't exist anymore, I think this Jira is a moot point in my point of view so hence it was closed. Since we moved to Apache, I would strongly advise us to allow the person who will be actually doing the work (to use Maven or not, etc.) the freedom to make this decision. --Pei -----Original Message----- From: Coarr, Matt [mailto:[email protected]] Sent: Thursday, August 23, 2012 4:59 PM To: [email protected] Subject: Re: cTAKES 2.6 - packaging of deliverable - was RE: [jira] [Closed] (CTAKES-34) icTAKES.jar is missing from the .gz distributions My vote is to continue in the direction of the previous vote -- one jar file produced for each module. This will align the development (svn trunk) work using either eclipse or the command line more closely with the execution of the binary release (jar only) environment. This will also set us up for a smooth migration to maven. My $0.02, Matt
