The compiler might generate diagnostics during compilation (for
example, error messages). If a diagnostic listener is provided,
the diagnostics will be supplied to the listener. If no listener
is provided, the diagnostics will be formatted in an unspecified
format and written to the default output, which is System.err
unless otherwise specified. Even if a diagnostic
listener is supplied, some diagnostics might not fit in a Diagnostic
and will be written to the default output.
A compiler tool has an associated standard file manager, which is the file manager that is native to the tool (or built-in). The standard file manager can be obtained by calling getStandardFileManager.
A compiler tool must function with any file manager as long as any additional requirements as detailed in the methods below are met. If no file manager is provided, the compiler tool will use a standard file manager such as the one returned by getStandardFileManager.
An instance implementing this interface must conform to
The Java Language Specification
and generate class files conforming to
The Java Virtual Machine Specification.
The versions of these
specifications are defined in the Tool interface.
Additionally, an instance of this interface supporting SourceVersion.
or higher must also support annotation processing.
The compiler relies on two services: diagnostic listener and file manager. Although most classes and interfaces in this package defines an API for compilers (and tools in general) the interfaces DiagnosticListener, JavaFileManager, FileObject, and JavaFileObject are not intended to be used in applications. Instead these interfaces are intended to be implemented and used to provide customized services for a compiler and thus defines an SPI for compilers.
There are a number of classes and interfaces in this package which are designed to ease the implementation of the SPI to customize the behavior of a compiler:
StandardJavaFileManager
The standard file manager serves two purposes:
Reusing a file manager can potentially reduce overhead of scanning the file system and reading jar files. Although there might be no reduction in overhead, a standard file manager must work with multiple sequential compilations making the following example a recommended coding pattern:
File[] files1 = ... ; // input for first compilation task File[] files2 = ... ; // input for second compilation task JavaCompiler compiler = ToolProvider.getSystemJavaCompiler(); StandardJavaFileManager fileManager = compiler.getStandardFileManager(null, null, null); Iterable<? extends JavaFileObject> compilationUnits1 = fileManager.getJavaFileObjectsFromFiles(Arrays.asList(files1)); compiler.getTask(null, fileManager, null, null, null, compilationUnits1).call(); Iterable<? extends JavaFileObject> compilationUnits2 = fileManager.getJavaFileObjects(files2); // use alternative method // reuse the same file manager to allow caching of jar files compiler.getTask(null, fileManager, null, null, null, compilationUnits2).call(); fileManager.close();
DiagnosticCollector
Iterable<? extends JavaFileObject> compilationUnits = ...; JavaCompiler compiler = ToolProvider.getSystemJavaCompiler(); DiagnosticCollector<JavaFileObject> diagnostics = new DiagnosticCollector<JavaFileObject>(); StandardJavaFileManager fileManager = compiler.getStandardFileManager(diagnostics, null, null); compiler.getTask(null, fileManager, diagnostics, null, null, compilationUnits).call(); for (Diagnostic<? extends JavaFileObject> diagnostic : diagnostics.getDiagnostics()) { System.out.format("Error on line %d in %s%n", diagnostic.getLineNumber(), diagnostic.getSource().toUri()); } fileManager.close();
ForwardingJavaFileManager
, ForwardingFileObject
, and
ForwardingJavaFileObject
final Logger logger = ...; Iterable<? extends JavaFileObject> compilationUnits = ...; JavaCompiler compiler = ToolProvider.getSystemJavaCompiler(); StandardJavaFileManager stdFileManager = compiler.getStandardFileManager(null, null, null); JavaFileManager fileManager = new ForwardingJavaFileManager(stdFileManager) { @Override public void flush() throws IOException { logger.entering(StandardJavaFileManager.class.getName(), "flush"); super.flush(); logger.exiting(StandardJavaFileManager.class.getName(), "flush"); } }; compiler.getTask(null, fileManager, null, null, null, compilationUnits).call();
SimpleJavaFileObject
/** * A file object used to represent source coming from a string. */ public class JavaSourceFromString extends SimpleJavaFileObject { /** * The source code of this "file". */ final String code; /** * Constructs a new JavaSourceFromString. * @param name the name of the compilation unit represented by this file object * @param code the source code for the compilation unit represented by this file object */ JavaSourceFromString(String name, String code) { super(URI.create("string:///" + name.replace('.','/') + Kind.SOURCE.extension), Kind.SOURCE); this.code = code; } @Override public CharSequence getCharContent(boolean ignoreEncodingErrors) { return code; } }
DiagnosticListener
, Diagnostic
, JavaFileManager
Modifier and Type | Class and Description |
---|---|
public static interface | JavaCompiler.
Interface representing a future for a compilation task. |
Modifier and Type | Method and Description |
---|---|
public StandardJavaFileManager | Returns: the standard file managera diagnostic listener for non-fatal
diagnostics; if diagnosticListener, Locale null use the compiler's default method
for reporting diagnosticsthe locale to apply when formatting diagnostics;
locale, Charset null means the default locale.the character set used for decoding bytes; if
charset)null use the platform defaultReturns a new instance of the standard file manager implementation for this tool. |
public JavaCompiler. | Returns: an object representing the compilationa Writer for additional output from the compiler;
use out, JavaFileManager System.err if null a file manager; if fileManager, DiagnosticListener<? super JavaFileObject> null use the
compiler's standard file managera diagnostic listener; if diagnosticListener, Iterable<String> null use the compiler's default method for reporting
diagnosticscompiler options, options, Iterable<String> null means no optionsnames of classes to be processed by annotation
processing, classes, Iterable<? extends JavaFileObject> null means no class namesthe compilation units to compile, compilationUnits)null means no compilation unitsCreates a future for a compilation task with the given components and arguments. |
getStandardFileManager | back to summary |
---|---|
public StandardJavaFileManager getStandardFileManager(DiagnosticListener<? super JavaFileObject> diagnosticListener, Locale locale, Charset charset) Returns a new instance of the standard file manager implementation for this tool. The file manager will use the given diagnostic listener for producing any non-fatal diagnostics. Fatal errors will be signaled with the appropriate exceptions. The standard file manager will be automatically reopened if
it is accessed after calls to
|
getTask | back to summary |
---|---|
public JavaCompiler. Creates a future for a compilation task with the given components and arguments. The compilation might not have completed as described in the CompilationTask interface. If a file manager is provided, it must be able to handle all
locations defined in Note that annotation processing can process both the
compilation units of source code to be compiled, passed with
the
|
Before calling the call
method, additional aspects of the
task can be configured, for example, by calling the
setProcessors method.
Modifier and Type | Method and Description |
---|---|
public void | addModules(Iterable<String>
the names of the root modules moduleNames)Adds root modules to be taken into account during module resolution. |
public Boolean | Returns: true if and only all the files compiled without errors; false otherwiseRedeclares java. Performs this compilation task. |
public void | |
public void | setProcessors(Iterable<? extends Processor>
processors (for annotation processing) processors)Sets processors (for annotation processing). |
addModules | back to summary |
---|---|
public void addModules(Iterable<String> moduleNames) Adds root modules to be taken into account during module
resolution.
Invalid module names may cause either
|
call | back to summary |
---|---|
public Boolean call() Redeclares java. Performs this compilation task. The compilation may only
be performed once. Subsequent calls to this method throw
|
setLocale | back to summary |
---|---|
public void setLocale(Locale locale) Sets the locale to be applied when formatting diagnostics and other localized data.
|
setProcessors | back to summary |
---|---|
public void setProcessors(Iterable<? extends Processor> processors) Sets processors (for annotation processing). This will bypass the normal discovery mechanism.
|