-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b91
-
generic
-
generic
-
Verified
javax.tools.StandardJavaFileManager is a bit hard to use. If we add a
few convenience method, we can avoid calls to Arrays.asList which
continuously clutter client code. Since StandardJavaFileManager is
API, not SPI adding a few convenience methods is fine.
javax.tools.JavaCompiler.CompilationTask should be a Callable, not a
Runnable. This will simplify the interface by reducing the method
count by one and works well with java.util.concurrent.FutureTask.
javax.tools.JavaCompiler.getStandardFileManager should have an
encoding argument.
From: Jonathan Gibbons <###@###.###>
Cc: Peter von der Ahe <###@###.###>
Subject: Re: RegularFileObject.toURI
Date: Tue, 23 May 2006 17:03:48 -0700
FileObject.toURI is somewhat underspecified. In particular, I think
it should say something about whether it is absolute or relative, and
if relative, relative to what context.
javax.tools.StandardJavaFileManager.setLocation should say that
setting a path will discard the previous.
few convenience method, we can avoid calls to Arrays.asList which
continuously clutter client code. Since StandardJavaFileManager is
API, not SPI adding a few convenience methods is fine.
javax.tools.JavaCompiler.CompilationTask should be a Callable, not a
Runnable. This will simplify the interface by reducing the method
count by one and works well with java.util.concurrent.FutureTask.
javax.tools.JavaCompiler.getStandardFileManager should have an
encoding argument.
From: Jonathan Gibbons <###@###.###>
Cc: Peter von der Ahe <###@###.###>
Subject: Re: RegularFileObject.toURI
Date: Tue, 23 May 2006 17:03:48 -0700
FileObject.toURI is somewhat underspecified. In particular, I think
it should say something about whether it is absolute or relative, and
if relative, relative to what context.
javax.tools.StandardJavaFileManager.setLocation should say that
setting a path will discard the previous.
- relates to
-
JDK-6420156 JSR 199: rename JavaCompilerTool to JavaCompiler
- Resolved