ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pei Chen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CTAKES-81) Update runctakesCPE/CVD startup scripts to use maven to resolve all of it's dependencies
Date Thu, 25 Oct 2012 21:49:12 GMT

     [ https://issues.apache.org/jira/browse/CTAKES-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Pei Chen resolved CTAKES-81.

    Resolution: Fixed

Fixed in r1398497.
New scripts have been added to /bin in the distribution
There is also and option to run it in maven with mvn -PrunCVD copile or -PrunCPE compile.

> Update runctakesCPE/CVD startup scripts to use maven to resolve all of it's dependencies
> ----------------------------------------------------------------------------------------
>                 Key: CTAKES-81
>                 URL: https://issues.apache.org/jira/browse/CTAKES-81
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-clinical-pipeline
>    Affects Versions: 2.6-incubating
>            Reporter: Pei Chen
>            Assignee: Pei Chen
>            Priority: Minor
>             Fix For: 3.0-incubating
> - Delete cTAKESCVDGUI.java and cTAKESCPEGUI.java; they look like a copy and paste of
org.apache.uima.tools.cvd.CVD, org.apache.uima.tools.cpm.CpmFrame.  Just launch the UIMA classes;
I couldn't see a need to have our own copies; if we really need to customize it, I would suggest
extended UIMA and override any special functionality.  Otherwise, we'll end up maintaining
these ourselves which is not ideal.
> - Add profiles the pom.xml to allow launch CVD, CPE from mvn using Maven to dynamically
resolve all of the required dependencies.  (We won't have to maintain yet another set of scripts
that contain dependencies or require some uber-jar.)
> - Update the existing runctakesCPE.sh, etc to use "mvn exec:exec -PrunCPE" instead.

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

View raw message