What a lightning fast answer! 👍 Thanks a lot!
I was just curious because we consider to move from gradle to maven at the moment to end all this gradle pain.

Maven also has it share of pains, just different ones :)

I'd rather have well documented maven pains shared by many other mavenmavens than be forced to use the build-system-du-jour. Really a pity that Realm Java now is not supported for the myriad of products and libraries that are maven based. Find a better solution. Supporting only gradle is wrong. Supporting a maven build artifact really opens realm to a much larger ecosystem. Which is right.

https://github.com/icon-Systemhaus-GmbH/javassist-maven-plugin this project might help, http://stackoverflow.com/questions/12423157/integrating-javassist-byte-code-manipulation-with-maven-compilation

Hey, I am also checking out about does realm support maven ? Here is my use case.

@cmelchior can you please help to figure out, how to support realm with sharable project lib models in android and java server projects?

@cmelchior now that Realm supports Linux (with RealmJS) and Win32 (with RealmJS), once #2339 is done, you also need to consider that most not-Android projects use Maven, not Gradle.

Sometimes we need to provide a jar to a third party, so the realm plugin does not support so that we can not use

Hi, any news?

Javassist seems to be supported with Maven, but I think the BytecodeTransformer was written in Groovy