[IMP]: Avoid maven for building packages

[luizluca]

Hello,

Maven is not a very "package build system" friendly. Normally a "package build system" does not even provide internet access (which is almost a requirement for maven).

If possible, could you include maven-generated files and/or replace buidling jar with standard tools? I guess only the JNI part really needs to be built specific for each system.

[RangerRick]

Since we a) want to deploy it to maven central and b) depend on at least one external library (SLF4J) changing the build is not really feasible (unless it's doing something else in addition which is kind of silly...)

Maven really is the "standard tool" for Java-with-dependencies, unless we were to move to gradle (which still relies on maven repositories in the end).

[luizluca]

Thanks @RangerRick ,

I'm starting to deal better now with maven. The process is something like:

1. predownload all maven deps for the project (Maven cannot download all depedencies with dependency:go-offline #3 makes this very difficult)
2. pack deps as a source
3. unpack on %prep
4. reconfigure maven to use this local repo (MAVEN_OPTS="-Dmaven.repo.local=/xxx")

It is still not great but, at least, it works ;-)