OK, so I read through the docs you linked to, and also took a look at the way you were using super-source in Emulation.gwt.xml in gwt-in-the- air:
http://code.google.com/p/gwt-in-the-air/source/browse/trunk/super/net/ltgt/gwt/air/emul/Emulation.gwt.xml I attempted to do the same thing with extended_JCL.gwt.xml, which pulls in the custom OutputStream class, as well as other resources: http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/bundles/org.eclipse.swt.e4.jcl/src/gwt/extended/common/extended_JCL.gwt.xml?view=markup I changed it to: <module> <source path="com/ibm/icu/text"/> <super-source/> </module> I'm now getting error messages like this: [java] [ERROR] Errors in 'jar:file:/C:/workspace-gsoc/ DojoResources/gwt/gwt-user.jar!/com/google/gwt/emul/java/util/ Iterator.java' [java] [ERROR] Line 16: The declared package "java.util" does not match the expected package "com.google.gwt.emul.java.util" [java] [ERROR] Errors in 'jar:file:/C:/workspace-gsoc/ DojoResources/gwt/gwt-user.jar!/com/google/gwt/benchmarks/translatable/ com/google/gwt/benchmarks/client/Benchmark.java' [java] [ERROR] Line 16: The declared package "com.google.gwt.benchmarks.client" does not match the expected package "com.google.gwt.benchmarks.translatable.com.google.gwt.benchmarks.client" As this is getting a bit complex, I feel like the thing to do is try to use super-source in a reduced case. But, I just have one question right now, which is, does super-source knock out *all* of the built-in emulation provided by GWT by "re-rooting" a source path? This is how I would interpret the above error output. If this is the case, is it not safe to use super-source more than once in a project? I'd greatly appreciate it if you would let me know what you think. Thanks, Jake On Apr 26, 5:58 pm, Jake <[email protected]> wrote: > @Thomas: That's probably exactly it. I'll review the documentation and > report back on whether I succeeded. > > Thank you for your help, > > Jake > > On Apr 26, 5:56 pm, Thomas Broyer <[email protected]> wrote: > > > On 26 avr, 08:34, Jake <[email protected]> wrote: > > > > Thomas and Vitali, thank you for the expert advice. I believe I'm > > > beginning to put this problem into perspective. Here is the > > > OutputStream implementation bundled with this project: > > > >http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/bundle... > > > > Here's the top-level module file I'm attempting to compile: > > > >http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/exampl... > > > > Finally, here's the module file which should pull in > > > OutputStream.java: > > > >http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.swt/exampl... > > > > My theory right now is that for some reason, our project's custom > > > OutputStream.java is not being found or used, and is therefore being > > > replace by GWT's built-in OutputStream class. But I'm not sure how > > > that could occur, as I know that GWT errors out if I specify a module > > > that it cannot find. So it seems that it must have found the module, > > > but is for some reason not using it in favor of its built-in > > > OutputStream class. Very strange. > > > If you re-define/emulate Java Runtime classes, you have to put them in > > a <super-source/> > > >http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
