[
https://issues.apache.org/jira/browse/CTAKES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732369#comment-16732369
]
James Joseph Masanz commented on CTAKES-76:
-------------------------------------------
stubs of classes that were in the above mentioned jars were added to
package org.apache.ctakes.assertion.stub
to allow for compilation.
To go back to using the original classes, look where ever there is an import of
something from
import org.apache.ctakes.assertion.stub.
and replace those with the appropriate imports.
See [Apache-SVN] Revision 1790058
specfically the imports that were changed here
[https://svn.apache.org/viewvc/ctakes/trunk/ctakes-assertion/src/main/java/org/apache/ctakes/assertion/medfacts/AssertionAnalysisEngine.java?r1=1790058&r2=1790057&pathrev=1790058]
When an assertion annotator is used that was part of medfacts/used jcarafe,
they now issue a warning
LOGGER.warn("This class cannot be used until CTAKES-76 is implemented.");
Related you might want to see CTAKES-435 which reported what happened when an
AE XML descriptor was using the assertion annotators that had to be removed.
> get third party dependencies into Maven Central
> -----------------------------------------------
>
> Key: CTAKES-76
> URL: https://issues.apache.org/jira/browse/CTAKES-76
> Project: cTAKES
> Issue Type: Bug
> Reporter: Steven Bethard
> Priority: Blocker
> Fix For: future enhancement
>
>
> There are lots of third party dependencies in cTAKES that aren't in Maven
> Central, e.g.
> OpenAI_FSM.jar
> FindStructAPI.jar
> SQLWrapper.jar
> lvg2010dist.jar
> med-facts-i2b2-1.2-SNAPSHOT.jar
> med-facts-zoner-1.1.jar
> jcarafe-core_2.9.1-0.9.8.3.RC4.jar
> jcarafe-ext_2.9.1-0.9.8.3.RC4.jar
> These are currently all referenced like:
> <dependency>
> ...
> <scope>system</scope>
> <systemPath>${project.basedir}/lib/OpenAI_FSM.jar</systemPath>
> </dependency>
> Now, when we release cTAKES, anyone who declares a Maven dependency on cTAKES
> will get errors, since none of these jars will be present.
> To fix this, we need to upload the third party jars to Maven Central. Full
> instructions are here:
> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
> Essentially, you create a minimal pom.xml for each library, and then run:
> mvn source:jar javadoc:jar package gpg:sign repository:bundle-create
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
