Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

JavaDoc not building on JitPack for v4

See original GitHub issue

Building the JavaDoc on JitPack does not work for v4 as you can see at https://jitpack.io/com/github/DV8FromTheWorld/JDA/v4-v3.7.1-g67c88d3-174/build.log. The problem is that you use -html5 JavaDoc option but do not configure JitPack to build on Java 9+. You can either do one of (or both)

Configure newer Java in jitpack.yml, for example like

jdk:
  - openjdk10

Make the -html5 switch dependent on the version built with, for example like

if (JavaVersion.toVersion(toolChain.version).java9Compatible) {
    addBooleanOption 'html5', true
}

Issue Analytics

State:
Created 5 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

Vampirecommented, Feb 9, 2019

So cut short, you don’t have any better idea and don’t want to improve on that, but thanks for the status heads-up.

(

Having a source that will not provide v3 docs in the future is not too nice, as my lib will still support v3 and it would be good if the links still work
Using IP based URL is bad for the very same reason domain names exist and this downtime shows
Downloading JARs and hosting them myself is bullshit and you know that, I just want to link from my documentation to your documentation reliably and not be a backup host for your server

)

May I ask why you think JitPack is not a good source for JavaDoc? Actually I think JitPack is generally not the best invention, but it is at least nice if there is no other option. javadoc.io is a great source for JavaDoc for all released versions, but for that as mentioned you would need to deploy to Maven Central (too).

0reactions

MinnDevelopmentcommented, Feb 9, 2019

I am just going to point out that the domain has already been updated to the new IP in a AAAA record.