You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to fix openjfx/openjfx-docs#44 in NetBeans and noticed that all the javafx-*-javadoc.jar files are identical and contain the full API documentation. The paths inside the jar are different from what the maven-javadoc-plugin generates, requiring knowledge of module names to resolve the correct .html file for a given .class.
It's not impossible to work around, but every tool has to do it. It would be nice for OpenJFX to integrate better with the ecosystem and behave more like every other library in this regard. What do you think?
The text was updated successfully, but these errors were encountered:
I created NETBEANS-3296 to track all the errors related to using the JavaFX Javadoc and Sources in NetBeans. An identical copy of the issue description is on GitHub at jgneff/netbeans-doc-src.
I'm trying to fix openjfx/openjfx-docs#44 in NetBeans and noticed that all the
javafx-*-javadoc.jar
files are identical and contain the full API documentation. The paths inside the jar are different from what the maven-javadoc-plugin generates, requiring knowledge of module names to resolve the correct.html
file for a given.class
.It's not impossible to work around, but every tool has to do it. It would be nice for OpenJFX to integrate better with the ecosystem and behave more like every other library in this regard. What do you think?
The text was updated successfully, but these errors were encountered: