-
Notifications
You must be signed in to change notification settings - Fork 15
Closed
Description
Discussion about support for this ongoing in the Discord thread:
JEP 467: Enhanced Markdown Comments
avaje-http
reads Javadoc for OpenAPI generation.
- If we modify the test suite to have a markdown version, Avaje build toolchain requires Java 25+ then
- If we bump that requirement, doesn't it also make sense for Avaje to start using that kind of doc internally too?
- I do not mind personally doing the boring refactoring to make all our Javadoc use the new format
- It is possible to use Markdown comments on an older Java release.
- You can even target Java 11 and use JDK 25 as your build toolchain, and use markdown comments.
- The only things this affects is - 1) cannot build Javadoc site without JDK 25 - 2) some people may have outdated IDEs?
Modifying the generator to support both Javadoc syntax should not be too difficult.
- We are only reading main Javadoc description - but I don't think the current solution supports e.g.
{@link }
? - We only read that up-to the last period (
.
)? - Stuff like
@return
,@param
is unchanged. We just need to be able to support both///
&/**
.
that something is not complex doesn't mean it can't be a lot of work :-)
Metadata
Metadata
Assignees
Labels
No labels