Maven artifacts

[ceharris]

This is a really nice library and I've been using it for a lot of years now.

Please please please get yourself set up to use Sonatype's OSS repository hosting so you can publish Mibble artifacts via Maven Central.

This will make it so much easier for open source libraries like Tnm4j to make use of Mibble without having to explain to developers how to manually install Mibble artifacts in their local repository.

[cederberg]

I'm not opposed to publishing Maven artifacts, but can't really find the time or interest in doing it myself.

If you feel strongly about this, you're be more than welcome to handle Maven publishing for the Mibble project. I can easily setup a maven@mibble.org mail alias if that would be of any help. Please let me know what you think.

[ceharris]

Looks like we could pretty easily modify Mibble's gradle build using the instructions in this blog post. After the project is registered with the Sonatype OSS, then publishing the artifacts is as easy as running a build.

I can help get everything set up if you don't have time or interest in doing it. And when there's a new release, if you don't want to upload the artifacts yourself (by running that part of the build), I can do that, too. I'll just need to know when you do a release.

[ceharris]

Could also add either modify your package.xml so that when packaging the public release it publishes the resulting artifacts, or make a separate publish.xml ant build that does it.

[ceharris]

Any more thoughts on this?

[cederberg]

Sorry for the delay. Email overload here.

The Gradle build was contributed sometime back, but I don't currently use or maintain it. I'm using the old robust Ant build files as they have knowns outcomes. But then again, Mibble dependencies or project structure doesn't change much so...

I think the best way for an automated integration would be in package.xml, as that contains the targets I use for building the release dist. Which I then manually upload to website + Github.