Deployment to public Maven repository

[AlexTGMM]

Is JTCL deployed to any public Maven repositories? If not, are there any plan to do so or reasons why it hasn't been done?

[dronox]

@TheGreatandMightyMe: I do not now if anyone is currently maintaining the jtcl project, but I forked the repo (https://github.com/dronox/jtcl) and made some code adaptions (to make it compile with Java 9+, and providing access to variable look-up at the current scope in the interpreter) and published jtcl to sonatype (sync to maven central was activated by sonatype, so it should be synced in some minutes): https://oss.sonatype.org/content/repositories/releases/com/github/dronox/jtcl

group id: com.github.dronox
artifact id: jtcl
version: 2.9.1

In order to include it in your sbt project you should add the following code snippet to your build.sbt:
libraryDependencies += "com.github.dronox" % "jtcl" % "2.9.1"

[tpoindex]

Hey Dustin, I would happily add you as a maintainer on the project if you are interested. Ton

…

On Tue, Nov 20, 2018, 17:35 Dustin Peterson ***@***.*** wrote: @TheGreatandMightyMe <https://github.com/TheGreatandMightyMe>: I do not now if anyone is currently maintaining the jtcl project, but I forked the repo (https://github.com/dronox/jtcl) and made some code adaptions (to make it compile with Java 9+, and providing access to variable look-up at the current scope in the interpreter) and published jtcl to sonatype (sync to maven central was activated by sonatype, so it should be synced in some minutes): https://oss.sonatype.org/content/repositories/releases/com/github/dronox/jtcl group id: com.github.dronox artifact id: jtcl version: 2.9.1 In order to include it in your sbt project you should add the following code snippet to your build.sbt: libraryDependencies += "com.github.dronox" % "jtcl" % "2.9.1" — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFfFGlTMtd3UGG404NM4rhweTSinlk9Yks5uxJ-3gaJpZM4THdQW> .

[dronox]

Hi Tom,
yes, I think this would be better than submitting things to a fork that is never merged back. :) Furthermore I can publish into group id com.github.jtcl-project which makes more sense, thanks!

BR, Dustin

[marinier]

Hi guys,

I'm also looking for a maven release of jtcl. I tried the 2.9.1 one referenced above, but unfortunately I need Java 8 compatibility, and that one requires java 9+. Would it be possible to either make a Java 8 build of 2.9.1, or would it be ok if I took the pre-built 2.8.0 release from here and put it on a public maven repo somewhere? (The issue is that our open source project, https://github.com/soartech/jsoar, doesn't build outside of our internal setup right now, because a few dependencies are not publicly available on maven, and we're trying to resolve that.)

Thanks,
Bob

[dronox]

Hi Bob,

sorry, I didn't have the time to publish under jtcl-project domain in maven, but the 2.9.3 version I published in maven under com.github.dronox is Java-8 compatible. Sorry for the confusion, I didn't track my Java version before but starting from 2.9.3 it should work - at least I am using it with Java 8 on some machines. I hope that I have time next month to publish under jtcl-project and then will make sure that it is Java-8-compatible. Until then you might use com.github.dronox.jtcl 2.9.3.

BR, Dustin

[marinier]

Awesome thanks! I've tested and it's working for me.

[dbohdan]

@tpoindex @dronox Could you merge the changes from https://github.com/dronox/jtcl/ into this repository? This would make it possible to build and test JTcl out of the box on an up-to-date system again.