ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Joseph Masanz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CTAKES-76) get third party dependencies into Maven Central
Date Thu, 18 Jul 2013 18:22:49 GMT

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

James Joseph Masanz commented on CTAKES-76:
-------------------------------------------


Info from Matt C:

The two med-facts jars are on maven central with a group id of "net.sf.mastif" and the two
artifact ids are "mastif-i2b2" and "mastif-zoner".  Both are version 1.4.  Same code, but
packaged up to meet maven central guidelines of having the project name and group id match
up with project structure and project hosting location.

The two jcarafe jars are also on maven central.  Group id is "net.sf.carafe.jcarafe" and the
artifact ids are "jcarafe-core_2.9.1" and "jcarafe-ext_2.9.1".  The version for both of them
is 0.9.8.3.RC4.


                
> 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.1
>
>
> 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 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

Mime
View raw message