I'm glad that you brought this up. Such reference card exists:
https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
Sorry for not finding it. Given wiki seems more or less organized by
project, would it be possible to add a wiki page for Jigsaw project and
reference this table from the added page. It would be an useful help.
We're updating this wiki as we identify new noteworthy ones.
com.sun.xml.txw2.output.IndentingXMLStreamWriter |
javax.xml.stream.XMLOutputFactory.setProperty(INDENT, true)
Is there a RFE for it? If not, can you submit one?
Done; Review ID: 9027107
---
After executing jdeps, I have found, in my code, only one other use case
of internal API (not described but useful): execution of javac/javadoc
to generate their output in-memory (no temporary write on the real file
system).
Currently, in my code, it is working (compilation of source classes and
generation of javadoc is done in-memory) using directly
com.sun.tools.javac.nio.JavacPathFileManager and an in-memory VFS
implementing NIO.2, then I use internal class
com.sun.tools.javac.nio.JavacPathFileManager. Currently javax.tools
provide only a File-based manager but no Path-based manager (javax.tools
was before NIO.2).
Given existing response [1] of Jonathan Gibbons, on this bug [2] planned
for Java 9 and visibly targeted now towards public API for a
PathFileManager, I have not opened another specific feature request for
public API corresponding com.sun.tools.javac.nio.JavacPathFileManager.
[1]: "The intent is that clients should be able to provide custom
Path-based file systems, and have access to a PathFileManager, but it
looks like we need to do more work in this area."
[2]: https://bugs.openjdk.java.net/browse/JDK-8029622
Thanks,
Daniel.
