Repository now that bintray shut down ?

[Folofietre]

Repository now that bintray shut down ?

[fluidsonic]

As there is no activity in this project I've forked and published it ​using my own group on Maven Central.
No need for any code changes as the Java package names stay the same.

It's available under io.fluidsonic.mirror:quartz-mongodb:2.1.0 and io.fluidsonic.mirror:quartz-mongodb:2.2.0-rc2.

The fork was made only for publishing. I'm not taking over as maintainer ;)

I hope @michaelklishin can publish it to Maven Central soon.
Feel free to copy my Gradle publishing configuration and set up OSSRH for your own domain.

[grenader]

@michaelklishin, It would be nice if you upload new versions to Maven Central or Clojars

[zoom2arun]

Same issue here. Please confirm if there is a new home where this is migrated?

[nolines]

Same here.

[Folofietre]

@michaelklishin any new about migrating the artifact repository ?

[Folofietre]

As a temporary solution, I forked this repo and followed the doc :
https://docs.gitlab.com/ee/user/packages/maven_repository/#publish-a-package

[arthursb14]

Same here.

[antpaw]

I really hope a more permanent solution can be worked out here.
I was able to fetch it form jitpack.io

	<repositories>
		<repository>
		    <id>jitpack.io</id>
		    <url>https://jitpack.io</url>
		</repository>
	</repositories>


	<dependency>
	    <groupId>com.github.michaelklishin</groupId>
	    <artifactId>quartz-mongodb</artifactId>
	    <version>2.1.0</version>
	</dependency>

you might want to fork and login to jitpack

[WakeCaine]

Solution would be to publish to Maven Central but that carries some work behind it and pretty much nobody but @michaelklishin or any authorized person by him, cant do. Or somebody could take the handle over and make fork of this fork and publish it.
Personally for our use we will most likely either publish on "our"(company) maven for private use or switch to sql version.