[
https://issues.apache.org/jira/browse/CTAKES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813259#comment-13813259
]
Newres Al Haider commented on CTAKES-76:
----------------------------------------
I am currently trying to get a fully mavenized build of cTakes up and running
and ran into this issue.
Having system scopes within the maven pom gives a lot of problems, so after
playing whack-a-mole with all the dependency issues that came up, I created
some minimal pom's for three of the dependencies that work from a remote
repository.
The biggest headache left at the moment is that the
med-facts-i2b2-1.2-SNAPSHOT.jar already contains a pom that refers to a remote
repository that I can not access. I am currently trying to change it's pom to
avoid issues with it, but it is a bit too complex to do at a first glance. It
also contains some hard coded paths to models, which I am sure could give some
issues at some point.
In addition the pom for the assertion module has issues (aside form the system
scope): versions parameter is missing, which makes it not go through any other
dependencies it needs.
> 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
>
>
> 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.1#6144)
