ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CTAKES-76) get third party dependencies into Maven Central
Date Mon, 03 Apr 2017 23:55:41 GMT

    [ https://issues.apache.org/jira/browse/CTAKES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954360#comment-15954360
] 

ASF subversion and git services commented on CTAKES-76:
-------------------------------------------------------

Commit 1790058 from james-masanz@apache.org in branch 'ctakes/trunk'
[ https://svn.apache.org/r1790058 ]

remove four 3rd-party jars (CTAKES-138) from Apache SVN. The code that uses those jars isn't
part of the default pipeline and predates the similar ctakes machine learning assertion tool.
 For now replace classes from those jars with stubs so compile works.   If those 3rd party
jars get added to maven (See CTAKES-76) we can add them back as proper maven dependencies
at that time.

> 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: 3.2.3
>
>
> 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
(v6.3.15#6346)

Mime
View raw message