Actually after poking around in Maven documentation I think I have just figured out an approach I like.
For each pipeline I wish to create, I will generate a Maven assembly descriptor. I will put each assembly file in the cTAKES root pom.xml. Hopefully this will create each pipeline for me when I run 'package'. This approach will still tie in nicely with the project object model/lifecycle of cTAKES, and generate all my custom jars as well. I will try it out and update this thread with the results Thanks, Rob On 9/9/13 10:38 AM, "Chen, Pei" <pei.c...@childrens.harvard.edu> wrote: >Hi Robert, > >Are you planning to a process to build everything from source? >Or were you planning to have a build process that combines the ctakes-*** >jars with your custom application jars? > >--Pei > >> -----Original Message----- >> From: Robert Spurrier [mailto:robert.spurr...@explorys.com] >> Sent: Monday, September 09, 2013 9:27 AM >> To: dev@ctakes.apache.org >> Subject: Creating Runnable .JARs From A Subset of cTAKES Maven Modules >> >> Good Morning! >> >> I am trying to use cTAKES tools on a distributed computing platform. I >>would >> rather not ship the entire compiled cTAKES package (~1.5 Gb) out to the >> shared cache when I only need a few annotators and their resources at a >> time. >> >> I should first mention that I am not very familiar with Maven. I >>recently >> upgraded cTAKES from v 2.5.0, where I was configuring smaller pipelines >> using ant build files. This process was cumbersome however, and I can >> appreciate the new modular Maven project layout. I just do not know how >> to effectively utilize it in a way that is flexible. >> >> Does anyone have any advice on how I can package subsets of cTAKES >> annotator modules and their dependencies/resources, so I can create >> 'thinner' custom pipelines that are geared towards specific tasks? >> >> For example, I might ultimately want a pipeline .JAR that contains the >>tools to >> RegEx Left Ventricular Ejection Fraction measurements from free text. In >> such a .JAR I would not need any of the dictionary resources or negation >> annotators, so they could be excluded. >> >> It looks like I could create Maven assembly plugin descriptors to >>generate >> these custom .JARs, but I would like to see if anyone here has any >> advice/caveats before I pursue this route. >> >> >> Thanks, >> Robert Spurrier
