Javadoc for API
Jorn Vernee
jorn.vernee at oracle.com
Tue Jan 28 12:28:29 UTC 2025
Hey Nir,
The jextract API has been neglected for a while (as you've found).
Initially it was a way of avoiding adding many flags to jextract, to do
things like filtering, renaming, and other things. The idea being that
if users wanted more control of what jextract did, they could use the
API. But, now it seems like we're moving in that direction any way, with
the JSON based configuration:
https://bugs.openjdk.org/browse/CODETOOLS-7903788
I think we need to re-asses which use cases the jextract API addresses,
and whether using jextract through the ToolProvider interface, with the
extended configuration options, is also an option.
IIRC your use case is filtering the jextract output, right? Do you think
it would be possible to use the ToolProvider interface with a
combination of --dump-includes, and automatically generated
--include-XXX flags, to achieve the same level of functionality?
Jorn
On 26-1-2025 08:51, Nir Lisker wrote:
> Hi,
>
> There are several public methods the JextractTool exposes. Please
> javadoc to these methods so tool users will know what they do and how
> to use them.
>
> Thanks,
> - Nir
More information about the jextract-dev
mailing list