[jira] [Commented] (CTAKES-76) get third party dependencies into Maven Central

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 1513637 from chenpei@apache.org in branch 'ctakes/trunk'
[ https://svn.apache.org/r1513637 ]

CTAKES-76 - The assertion jars have not been moved to Maven Central yet!  Therefore, we still need the fileSets copied over to the distribution binary.
                
> 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