Problem linking to libraries using Maven

48 views
Skip to first unread message

Travis Good

unread,
Jul 10, 2014, 10:21:48 PM7/10/14
to scalanlp...@googlegroups.com
Hello,
I'm trying to use the following POM file along with maven to link the libraries associated with this project (EPIC). I'm using Scala 2.11. Unfortunately, I get the following error:

missing artifact com.typesafe.sbt: sbt-pgp: jar: 0.8.3

I've tried updating the project, to no avail. I found a copy of the jar and stuck it in the appropriate maven directory and refreshed, but this didn't do anything either. Am I forced to use SBT to use this library?

Thanks,

T.


pom.xml

David Hall

unread,
Jul 10, 2014, 10:51:51 PM7/10/14
to scalanlp...@googlegroups.com
Sorry, this is a known bug. I need to republish the artifacts. Can you try using 0.2-SNAPSHOT?

Also, Epic is only built against 2.10 right now, and Scala isn't binary compatible between 2.10 and 2.11. It should be an easy enough fix.

-- David

Travis Good

unread,
Jul 10, 2014, 11:18:49 PM7/10/14
to scalanlp...@googlegroups.com, dl...@cs.berkeley.edu
Hi David,
under Eclipse, it appears that the IDE does not support running multiple Scala versions. There is a hack available to try to maintain compatibility:
I tried this without success. I also tried linking to .2 SNAPSHOT versions but none of the dependencies could be resolved (Maven central lag, perhaps?)

I guess in order to try the library I will have to run an entirely separate instance of Eclipse or something, as my other projects depend on 2.11. Do you have any plans in the near future to migrate? Or any other workaround? Really appreciate the help. 

All the Best,
T.

David Hall

unread,
Jul 11, 2014, 1:10:59 PM7/11/14
to scalanlp...@googlegroups.com
I'll try to get this done this weekend.

David Hall

unread,
Jul 14, 2014, 12:16:34 PM7/14/14
to scalanlp...@googlegroups.com
this should be fixed, fwiw.

Travis Good

unread,
Jul 14, 2014, 6:34:30 PM7/14/14
to scalanlp...@googlegroups.com, dl...@cs.berkeley.edu
Great to hear. I'll try and test it out tonight. 

Thanks David!

Kind Regards,
Travis

Travis Good

unread,
Jul 15, 2014, 9:35:25 PM7/15/14
to scalanlp...@googlegroups.com, dl...@cs.berkeley.edu
Hi David,
I can't find the updated repo either here:

or here:
http://mvnrepository.com/artifact/org.scalanlp/epic_2.10/0.1

Ok. So, at this point I'm thinking I will try to simply add a Github resolver:

But alas, it appears there is no structure like this setup on your github. So it appears I can't get the current version of the library working with Maven. I guess I will try and clone and build it, but is there some other way you can force the maven central repos to update?

All the Best,
T.



On Monday, July 14, 2014 11:16:34 AM UTC-5, David Hall wrote:

Travis Good

unread,
Jul 15, 2014, 9:39:13 PM7/15/14
to scalanlp...@googlegroups.com, dl...@cs.berkeley.edu
Looking through the links, it appears that you need to run some mvn deploy type command to get it to a central repo. Not an expert at that part of the process, however.

David Hall

unread,
Jul 15, 2014, 10:36:43 PM7/15/14
to scalanlp...@googlegroups.com
Yeah, sorry, I didn't issue a release. I've republished a 0.2-SNAPSHOT. You'll need to use the Sonatype Repo or run sbt publish-local on a clone of epic.

resolvers +=  "Sonatype Snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/"

Reply all
Reply to author
Forward
0 new messages