Hi Devs, Please jitpack does not serve the build artefact of the version 1.5.1 of the java algorand SDK, even though it serves the version 1.5.0 properly, I just went through the logs of the build and there are two causes of the failure to serve the build artifact:
Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project algosdk: Fatal error compiling: invalid flag: --release ->
Jitpack seems to use an older version of Java than we do to publish binaries. You can ask them to use a newer version of Java, build the binaries yourself, or use the binaries we publish on maven.
All build tools that I’m aware of have a mechanism for pulling binaries from maven. Could you explain the benefit of jitpack as an alternative so that we can prioritize whether it should also be a tool we support?
@will Jitpack helps serve the build artifact of remote repositories in a gradle project, even if they are Maven Projects, It’s really useful for android developers. It’s similar to Jcentre or MavenCentral, or is the java-algorand-sdk distributed over Jcentre or MavenCentral?
Or do you have a better suggestion of how we can drag in the java-algorand-sdk in android studio without Jitpack? Please if you do, let me know.
Thanks