ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Finan (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CTAKES-437) lvg-dist version error when starting CVD or CPE profile
Date Fri, 28 Apr 2017 13:53:04 GMT

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

Sean Finan resolved CTAKES-437.
       Resolution: Pending Closed
    Fix Version/s: 4.0.1

Requires additional testing.  Testing will be passive by users of trunk cpe, cvd profiles

> lvg-dist version error when starting CVD or CPE profile
> -------------------------------------------------------
>                 Key: CTAKES-437
>                 URL: https://issues.apache.org/jira/browse/CTAKES-437
>             Project: cTAKES
>          Issue Type: Bug
>          Components: ctakes-clinical-pipeline
>    Affects Versions: 4.0.0
>            Reporter: Sean Finan
>            Assignee: Sean Finan
>            Priority: Critical
>              Labels: easyfix, patch
>             Fix For: 4.0.1
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Many thanks to Thomas W Loehfelm for reporting the problem and a fix:
> I received an error message when trying to runCVD due to a missing dependency version
in the clinical pipeline pom.xml file
>      *   Error message:
> "The project org.apache.ctakes:ctakes-clinical-pipeline:4.0.1-SNAPSHOT (<my ctakes
dir>) has 1 error 'build.plugins.plugin[org.codehaus.mojo:exec-maven-plugin].dependencies.dependency.version'
for gov.nih.nlm.nls.lvg:lvgdist:jar is missing. @ org.apache.ctakes:ctakes-clinical-pipeline:[unknown-version],
<my ctakes dir>/ctakes-clinical-pipeline/pom.xml, line 174, column 20
>      *   Fix:
> Add "<version>2016.0</version>" for that dependency in pom.xml (line 177)
> It seems that lvgdist is actually unnecessary for CPE and CVD, I my tests removing the
dependency had no ill effects.  From James Masanz:
> Looks like it's a left over from when we switched from using a local copy of LVG jar
in a local lib directory to using a maven dependency several years ago.
> It seems that the fix is actually to remove the dependency.

This message was sent by Atlassian JIRA

View raw message