powered by Jive Software

Openfire 4.3.2 in Maven Central repository


I was checking if I could find the lastest release of Openfire in Maven Central repository and it seems the last version available is the 4.2.0 :
[https://search.maven.org/search?q=g:org.igniterealtime.openfire](http://Maven Central Repo)

Do you think it would be possible for you guys to update the latest version of Openfire (and possibly the plugins if it’s doable) ? I need this so we could add openfire in our automation jobs for deployments.

Let me know if I can help,


@guus - I think this is something you probably need to setup, if it’s possible. Could help cut-down load on the main Ignite Realtime server.

@Bpt - Whilst you’re waiting, you should be able to fetch the current versions from the Ignite Realtime repo at https://igniterealtime.org/archiva/repository/maven/ - just add that to your list of repo’s in your Maven/Gradle/etc. config. Ideally last.

It contains both the server itself … https://www.igniterealtime.org/archiva/#artifact/org.igniterealtime.openfire/xmppserver

As well as the plugins … https://www.igniterealtime.org/archiva/#browse/org.igniterealtime.openfire.plugins

[EDIT: Correct the Repo URL]


Thank you for this @gdt , I had missed this when looking at OF sources.


First link should have archiva in it?

Also maybe we should add this info to https://github.com/igniterealtime/Openfire/blob/master/README.md ?

1 Like

Thanks, you’re quite right, URL now corrected.

@wroot are you asking for the link I posted ?

If yes, then yes I think it would be nice to have it in Maven Central. And if you do so, yes it should remove a lot of requests on your internal Maven repo.

I believe it’s possible to have this step (pushing to Maven central) done automaticaly with the good configuration in Openfire pom.xml. But not sure how you can handle the plugins.

No i was just replying to gdt. He has since fixed his URL (archiva folder was missing).

I’m not a developer or know much about Maven, so will leave it for gdt and Guus to setup.

It’s do-able, but a hassle. For now, I’m not to worried about the load on our server, nor am I inclined to spend time on publishing to Maven central, unless someone brings good arguments. :slight_smile:

Ah, when we get 5,000 developers all hitting the Ignite Realtime repo, then you’ll regret not doing it :wink:


Speaking about 5000 developers. Maybe putting it on Maven Central will give us better exposure?

Unlikely, IMHO. You don’t stumble across software in an artefact repo, there’s simply too much there. You have to know what you’re looking for.