Thanks for putting this together, Troy. Fwiw, the checkout URL on the guide (https://svn.apache.org/repos/asf/incubator/ctakes/tags/ctakes-3.0.0-incubating) doesn't exist. Not sure if it's meant to at some point or not.
Do we want devs checking out from tags instead of from trunk? Scott -----Original Message----- From: Bleeker, Troy C. [mailto:[email protected]] Sent: Friday, January 18, 2013 2:48 PM To: '[email protected]' Subject: cTAKES 3.0 developer guide review The developer guide is pretty close to complete then. If anyone could take the time to review it, make changes. There are both expert install instructions and step by step. https://cwiki.apache.org/confluence/display/CTAKES/cTAKES+3.0+Developer+Guide I used what we think will be the URL for check out based on what James said. Fill me in on how to select which run configuration and I can add it - or the beauty of the wiki - you can too. I assume someone will take care of deleting the empty directories at some point. For the launch files I think there should only be 2 as well. Are these names better than what's there now, more descriptive in the short space? UIMA_GUI_collection_processing_engine.launch UIMA_GUI_CAS_visual_debugger.launch Thanks Troy -----Original Message----- From: ctakes-dev-return-1053-Bleeker.Troy=mayo....@incubator.apache.org [mailto:ctakes-dev-return-1053-Bleeker.Troy=mayo....@incubator.apache.org] On Behalf Of Masanz, James J. Sent: Friday, January 18, 2013 12:08 PM To: '[email protected]' Subject: RE: cTAKES 3.0 questions There is a branch for 3.0 https://svn.apache.org/repos/asf/incubator/ctakes/branches/ctakes-3.0.0-incubating For each release candidate there is a tag such as https://svn.apache.org/repos/asf/incubator/ctakes/tags/ctakes-3.0.0-incubating-rc5 I'm assuming we will create a tag for the release without 'rcX' on the end once the release is approved. I don't think we need to document all the run configurations. I think we should just document how to select which one of the twin to select Within the Run Configurations popup, look at the Shared file field on the Common tab. Yes, all the institutional directories are supposed to be gone. Looks like we missed an empty one. Regards, James Masanz > -----Original Message----- > From: ctakes-dev-return-1048-Masanz.James=mayo....@incubator.apache.org > [mailto:ctakes-dev-return-1048-Masanz.James=mayo....@incubator.apache.org] > On Behalf Of Bleeker, Troy C. > Sent: Friday, January 18, 2013 11:29 AM > To: [email protected] > Subject: cTAKES 3.0 questions > > Working through the dev install instructions I've come up with a number of > questions. Could the group help me out ... > > Where will the non-volatile cTAKES 3.0 trunk be? Seems like the code here > keeps changing: > https://svn.apache.org/repos/asf/incubator/ctakes/trunk > Once released will the code freeze at a particular place and will it have > 3.0 in the URL in order to distinguish this release from an inevitable > future release? > > Why are there 4 .launch files under ctakes-clicnical- > pipeline/resources/launch? What's the difference? > CPE cTAKES.launch > CVD cTAKES.launch > UIMA_CPE_GUI--clinical_documents_pipeline.launch > UIMA_CVD--clinical_documents_pipeline.launch > > There are lots of Run Configurations now. Do we need a place to document > all of those? All of them in my checkout on 1/14 appear to have a twin. > > Ctakes/ctakes-ne-contexts/target/classes/edu/mayo/bmi is created in my > Eclipse projects upon checkout. Are not all the institutional directories > supposed to be gone? > > Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical Statistics and > Informatics > Phone: 507-293-1574 * Fax: 507-284-0360 * [email protected] Mayo > Clinic * 200 First Street SW * Rochester, MN 55905 * www.mayoclinic.org ________________________________ GHC Confidentiality Statement This message and any attached files might contain confidential information protected by federal and state law. The information is intended only for the use of the individual(s) or entities originally named as addressees. The improper disclosure of such information may be subject to civil or criminal penalties. If this message reached you in error, please contact the sender and destroy this message. Disclosing, copying, forwarding, or distributing the information by unauthorized individuals or entities is strictly prohibited by law.
