On APIdia there are now quick-selectors for Jakarta EE 11 API docs to reduce the view to core or web profile. You can also select e.g. platform without core and web to see precisely those modules that are *only* available in the full platform profile.
#java #javadoc #jakartaee

JakartaEE 11 docs on APIdia:
https://apidia.net/mvn/jakarta.platform/jakartaee/11
Note: If you visited the site recently, it may be necessary to reload with ctrl-F5 to get this new feature working. (That forces your browser to reload cached resources such as Javascript files.)

Jakarta 11 has been released! Congrats @jakartaee and OmniFish for getting this shipped!

API documentation is readily available on APIdia:
https://apidia.net/mvn/jakarta.platform/jakartaee/11

Compared to the official Javadocs, the docs on APIdia include the module pages, yet integrated into one coherent doc profile. E.g. check the new spec jakarta-data: https://apidia.net/mvn/jakarta.platform/jakartaee/11.0.0/?pck=jakarta.data-all-classes&cls=jakarta.data-module

#java #javadoc #jakartaee #jdk

Flexmark is a CommonMark/Markdown parser for Java, offering granular control of the parsing process, HTML rendering, emulation of other parsers, conversion modules e.g. to PDF or DOCX and a vast set of extension modules. The full flexmark module family is available on APIdia for browsing API docs in a single integrated doc profile: https://apidia.net/mvn/com.vladsch.flexmark/flexmark-all

#java #javadoc #markdown #jdk #flexmark

We made it to JFX-Central links of the week once again!
https://foojay.social/@frankdelporte/114635312724814686

Thank you, JFX-Central and all authors of the linked projects and articles, for keeping Java FX vivid and enabling Java on the frontend!
#javafx #LinksOfTheWeek #java #jdk #javadoc

We recently added API docs for the JavaFX components by DLSC, e.g. for PDF viewing, form-based UIs, preferences, picker controls and more. These controls are frequent and crucial building blocks of advanced JavaFX applications.
#javafx #java #jdk #javadoc

afterburner: https://apidia.net/mvn/com.dlsc.afterburner/afterburner.fx
forms: https://apidia.net/mvn/com.dlsc.formsfx/formsfx-core
gems: https://apidia.net/mvn/com.dlsc.gemsfx/gemsfx
keyboard: https://apidia.net/mvn/com.dlsc.keyboardfx/keyboardfx
pdfview: https://apidia.net/mvn/com.dlsc.pdfviewfx/pdfviewfx
picker: https://apidia.net/mvn/com.dlsc.pickerfx/pickerfx
phonenumber: https://apidia.net/mvn/com.dlsc.phonenumberfx/phonenumberfx
preferences: https://apidia.net/mvn/com.dlsc.preferencesfx/preferencesfx-core
retrofit: https://apidia.net/mvn/com.dlsc.retrofitfx/retrofitfx
showcase: https://apidia.net/mvn/com.dlsc.showcasefx/showcasefx
unit: https://apidia.net/mvn/com.dlsc.unitfx/unitfx
workbench: https://apidia.net/mvn/com.dlsc.workbenchfx/workbenchfx-core
GMaps: https://apidia.net/mvn/com.dlsc/GMapsFX

Just wasted >7 hours wondering why #Maven failed to generate my JavaDoc with #PlantUML class diagrams.

The reason? For unknown reason, #UMLDoclet (a plugin for JavaDoc used to generate the diagrams) throws an IllegalArgumentException if you set #JavaDoc's output level to “verbose”. 🤡 😭

This issue is known and had supposedly been fixed in 2024 but the fix does not appear to actually work: https://github.com/talsma-ict/umldoclet/issues/633

I will never understand teams that don't believe in writing #javadoc. You may think your code is SeLf dOcUmeNtIng, but it's not. It never is. It's always a lie you tell yourself.

For the love of all that is good, at the very least explain *what a class is for* and how it fits into the bigger picture.

Even if you think it's obvious. Nay, especially then!! I assure you, it won't be obvious to you in 5 years time, nor to the new guy inheriting your spaghetti in 10 years time.

#java