Hi Dima,

Most likely things are now out-of-sync since we have 4.0.1-SNAPSHOT.

Since it is just a sandbox project I didn't pay it any attention wrt the 4.0 
release.  It probably needs to be updated.

Anyway, you probably get the idea - instead of just adding 
"ctakes-clinical-pipeline" as a dependency, one can grab this pom, rename and 
uncomment as necessary.

Thanks for the update.  When Trump lands us on Mars I'll update the sandbox 
project.

Sean

-----Original Message-----
From: Dligach, Dmitriy [mailto:[email protected]] 
Sent: Friday, April 28, 2017 6:00 PM
To: [email protected]
Subject: Re: cTAKES as a dependency

Hi Sean,



Thanks for the pointers.



> There is a tiny module in ctakes sandbox named ctakes-the-api.  It consists 
> of a simple pom.xml that can be used to do exactly what interests you.  
> Download that pom and look at the comments inside.  It should be pretty 
> self-explanatory.



I tried this. It works, but only if I run ‘mvn clean compile’ in ctakes trunk 
first (which deposits a bunch of jars into my .m2 directory). If I remove .m2 
and try to build an empty directory with you pom.xml file, I get an error 
(pasted below). Is it possible it build fine on your end because there’s 
already ctakes-related stuff in your .m2?



[INFO] Scanning for projects...

[ERROR] [ERROR] Some problems were encountered while processing the POMs:

[FATAL] Non-resolvable parent POM for 
org.apache.ctakes:ctakes-the-api:[unknown-version]: Could not find artifact 
org.apache.ctakes:ctakes:pom:3.2.3-SNAPSHOT and 'parent.relativePath' points at 
wrong local POM @ line 6, column 12

 @

[ERROR] The build could not read 1 project -> [Help 1]

[ERROR]

[ERROR]   The project org.apache.ctakes:ctakes-the-api:[unknown-version] 
(/home/dima/Temp/pom.xml) has 1 error

[ERROR]     Non-resolvable parent POM for 
org.apache.ctakes:ctakes-the-api:[unknown-version]: Could not find artifact 
org.apache.ctakes:ctakes:pom:3.2.3-SNAPSHOT and 'parent.relativePath' points at 
wrong local POM @ line 6, column 12 -> [Help 2]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please 
read the following articles:

[ERROR] [Help 1] 
https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_confluence_display_MAVEN_ProjectBuildingException&d=DwIGaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao&m=_cciP59cAVa5JVLoMznmZU7g0s6FlhjClbuWDboQjkw&s=Vaf6Gt1ysN0Lsva2fO-HqYsucLD39WUyqox3r1K9uxU&e=
 

[ERROR] [Help 2] 
https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_confluence_display_MAVEN_UnresolvableModelException&d=DwIGaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao&m=_cciP59cAVa5JVLoMznmZU7g0s6FlhjClbuWDboQjkw&s=tY0paD2j0h-Ot0HDbVi8UM20cBgK_zmgAJCMIF5stvw&e=
 

Reply via email to