This review is dead. See
http://gwt-code-reviews.appspot.com/1217801/show
http://gwt-code-reviews.appspot.com/1188802/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
You cannot build the TypeOracle using the class bytes using the
classpath only, because of the re-rooted resources which have no
compiled classes near the source file. So, as part of the GWT Designer I
implemented disk caching of the compiled CompilationUnits. The CU caught
after compiling and
On 2010/12/07 13:53:13, alexander.mitin wrote:
You cannot build the TypeOracle using the class bytes using the
classpath only,
because of the re-rooted resources which have no compiled classes near
the
source file.
Good point. I'm using this method of getting byteCode just for the
On Tue, Dec 7, 2010 at 3:11 PM, zun...@google.com wrote:
On 2010/12/07 13:53:13, alexander.mitin wrote:
You cannot build the TypeOracle using the class bytes using the
classpath only,
because of the re-rooted resources which have no compiled classes near
the
source file.
Good point.
This change is not all the way ready for review, but I wanted some
feedback on the testing portion.
The overall aim of this change is to isolate the part of building the
type oracle that relies on running the JDT compiler from the part that
builds the type oracle from bytecode.
The idea is to
http://gwt-code-reviews.appspot.com/1188802/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Looks like this is heading in a good direction. Idea for the test code.
Another high level idea is that you a single test case superclass with
the bulk of the code, then you have to two subclasses that only differ
in how typeOracle is built. We use this pattern in other places.
