Add (preferably) Maven, Gradle or Ivy support

[pingidentity]

Add (preferably) Maven, Gradle or Ivy support

[dirmgr]

LDAP SDK releases are published in the Maven central repository with a group ID of "com.unboundid". The Standard Edition has been published there since version 1.1.1 and has an artifact ID of "unboundid-ldapsdk". The Minimal and Commercial Editions have been published there since version 3.0.0 and have artifact IDs of "unboundid-ldapsdk-minimal-edition" and "unboundid-ldapsdk-commercial-edition", respectively.

[iirekm]

But the problem is: I want to make a small bugfix in unboundid and install it to my local maven repo (to be able to use this changed version in my other maven projects). Because you didn't provide any pom.xml or build.gradle files it's impossible. The way how you publish to central Maven repos is irrelevant to me, I just want to publish my changes to my own local maven repo and to company's Nexus, and maybe then after some time create a pull request and then you can push this bugfix to maven central.

Why can't you just do it, pom.xmls are much simpler to create than those all big Ant build.xmls

[dirmgr]

If you've found a bug in the code, then please report it so that it can be fixed. I don't understand why you think that creating your own fork is a better option than having the upstream code get fixed so that you benefit along with everyone else. And I really don't understand why you expect a project's maintainer to help you fork that project on top of that.

At any rate, the current build process should provide everything you need to deploy to a Maven repository. Just running the provided build.sh shell script (or build.bat on Windows) will create Maven jar files in the build/package directory (one for the Standard Edition, one for the Minimal Edition, and one for the Commercial Edition). Each of these jar files contains a POM along with binary, source, and Javadoc jars.