I'm uneasy about that but I can't explain why exactly. I would be more comfortable having the dependencies match/describe the real dependencies.
________________________________________ From: ctakes-notifications-return-399-Masanz.James=mayo....@incubator.apache.org [ctakes-notifications-return-399-Masanz.James=mayo....@incubator.apache.org] on behalf of Pei Chen (JIRA) [[email protected]] Sent: Wednesday, February 20, 2013 8:30 PM To: [email protected] Subject: [jira] [Commented] (CTAKES-165) no maven profiles for running via maven other than mvn -PrunCPE and mvn -RrunCVD which are in ctakes-clinical-pipeline [ https://issues.apache.org/jira/browse/CTAKES-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582813#comment-13582813 ] Pei Chen commented on CTAKES-165: --------------------------------- should we just add all available modules as a dependency in the ctakes-clinical-pipeline? irrespective if it's used or not... > no maven profiles for running via maven other than mvn -PrunCPE and mvn > -RrunCVD which are in ctakes-clinical-pipeline > ---------------------------------------------------------------------------------------------------------------------- > > Key: CTAKES-165 > URL: https://issues.apache.org/jira/browse/CTAKES-165 > Project: cTAKES > Issue Type: Bug > Components: ctakes-drug-ner, ctakes-pad-term-spotter, > ctakes-relation-extractor, ctakes-side-effect, ctakes-smoking-status > Affects Versions: 3.0-incubating > Reporter: James Joseph Masanz > Priority: Minor > > It would be good to have other profiles than just those in > ctakes-clinical-pipeline > The two existing profiles don't compile some of the other components like > ctakes-drug-ner or ctakes-relation-extractor and since the existing ones are > in ctakes-clinical-pipeline they don't have everything on the classpath > needed to run those other components. > I noticed this while I was running > mvn -PrunCVD compile > and tried to load the relation extractor aggregate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
