Hi Grzegorz, You mentioned the compiled classes in the class path are used to populate the type orace. For the most part, the type oracle types are compiled from source. Types that don't have source are then checked to see if they are binary annotations and then a type oracle reference is entered.
Could it be true that scala-library.jar contains both libraries to use with the GWT compiler and some sort of runtime environment (sources) to compile with your app? If so, maybe the solution is to split scala-library.jar into the equivalent of 'dev' and 'user' components, such that 'user' is not needed for running the compiler and 'dev' is not needed for the app to link against. On Mon, May 23, 2011 at 6:29 PM, Grzegorz Kossakowski <[email protected]> wrote: > Hello, > > I run into a case when I want to have different classpath for running > gwtc (through com.google.gwt.dev.Compiler class) from classpath > containing source code that gwtc would compile. > > Let me give you a specific scenario. My fork of gwt is using > scala-library.jar of some version A for implementing internals of > gwtc. Now application that gwtc should compile uses different version > B of scala-library.jar that is binary incompatible with A. Is it > possible to run gwtc so it uses A for it's own execution but uses B > for JDT execution, populating TypeOracle, etc.? > > One thing that's worth mentioning: I'm talking here about compiled > classes in classpath because they are used to populate TypeOracle. > Source code (used for constructing GWT AST nodes) is in one copy > corresponding to version B. > > -- > Grzegorz Kossakowski > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- Eric Z. Ayers Google Web Toolkit, Atlanta, GA USA -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
