-
Notifications
You must be signed in to change notification settings - Fork 56
Maven central release setup #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maven central release setup #67
Conversation
1f2fc4b to
c4b597e
Compare
c4b597e to
1b91815
Compare
|
My main concern with this PR is whether or not the native libraries will still be placed in the right location. It'd also be nice to see Travis-CI in a better state (to no fault of yours) before merging. For starters, Travis bumped the build environment (14.04 -> 16.04), so
|
1b91815 to
ae9e4cb
Compare
|
Looks like Travis is building with JDK12+ while the compilation target of 1.6 is only supported up to JDK11(LTS).
|
|
Fixed via d0c6223. |
ae9e4cb to
1d76c2a
Compare
This was done intentionally via #55 although I'm open to ideas.
Between Travis, Maven and CMake, the build environment is quite hard for even me to follow, especially when it's only touched on occasion. From what I recall correctly, the system was only written with developers (not releases) in mind and assumed a standard Maven setup, CMake installed from the website and some -- any version -- of MSVC available. I'm sure this can be improved and as I begin working on |
Updates the project to conform with Maven Central requirements
Edit: See also #23 (comment)