As noted at the Forum, a new Javadoc .jar file (and a corresponding .jar.asc) is deployed for each new version of most packages (in the org.jmonkeyengine repo at BinTray/JCenter) but not for jme3-examples.
To see this, browse to https://bintray.com/jmonkeyengine/org.jmonkeyengine/jme3-examples/3.3.2-stable#files/org%2Fjmonkeyengine%2Fjme3-examples%2F3.3.2-stable
This looks to be intentional. jme3-examples/gradle.properties has:
# When running this project we don't need javadoc to be built.
buildJavaDoc = false
The rationale isn't clear to me. Why do other subprojects need javadoc but not this one?
As noted at the Forum, a new Javadoc .jar file (and a corresponding .jar.asc) is deployed for each new version of most packages (in the org.jmonkeyengine repo at BinTray/JCenter) but not for jme3-examples.
To see this, browse to https://bintray.com/jmonkeyengine/org.jmonkeyengine/jme3-examples/3.3.2-stable#files/org%2Fjmonkeyengine%2Fjme3-examples%2F3.3.2-stable
This looks to be intentional. jme3-examples/gradle.properties has:
The rationale isn't clear to me. Why do other subprojects need javadoc but not this one?