Hi all, Thanks again for the responses. See my replies below:
On Fri, May 15, 2009 at 5:51 AM, Thomas Broyer <[email protected]> wrote: > > > > On 15 mai, 03:06, Alyxandor <[email protected]> wrote: >> Are you getting a "wrong package error"? Because if you aren't, you >> should! > > Actually, I'd rather say you shouldn't add your "super" to the > projects build path (no need to compile the classes to Java .class, > with the risk of having them used in place of the Java runtime's ones; > only the source is needed, and only for the GWT Compiler, so what's > needed is that the "super" is in the classpath, not the build path!) OK, that's very interesting! The distinction between the classpath and the build path was not something that was clear to me before. Now, I believe it is, but I'm not sure, how do you add a path to the classpath without adding it to the build path in Eclipse? The GWT module still needs to be found on the classpath. I took a look at the .classpath from gwt-in-the-air: http://www.google.com/codesearch/p?hl=en#7KCk1V3Al4I/trunk/.classpath&q=.classpath%20package:http://gwt-in-the-air\.googlecode\.com It doesn't appear to reference super. Is this because .classpath sets the project build path in Eclipse? How do you then set the classpath so that the Emulation.gwt.xml module is finable, but not on the build path? > (however, adding it to the build path in Eclipse brings you better > editing, with better code completion, etc.) > > Finally, it's more a matter of taste than a "rule" or even "best > practice"; but you have to understand what it means when you add the > "super" to the build path or not. I still don't have a clear sense of this. What would you say it means to add "super" to the build path? > >> Also, you've got to make your java.io hack-pack-age another level >> deeper... > > Not necessarily. GWT's Emul package uses <super-source/>, and so do I > in GWT-in-the-AIR (cf. > http://code.google.com/p/gwt-in-the-air/source/browse/trunk/super/net/ltgt/gwt/air/emul/ > ) I still can't seem to get that to work :( Not sure why, but my use of the empty <super-source/> tag always causes GWT to fail. This is unfortunate, as it seems like it would be the best way to make both GWT and the IDE happy. So, for example, with gwt-in-the-air, my approach would have been to add /super/net/ltgt/gwt/air/emul/ as a source folder (so, on the build path). Then the emulated packages would be of the form java.*, which would correspond to the declared package names in the *.java files. This makes the IDE happy, and in my mind, it seems like GWT shouldn't have a problem with it either. But, so far, this approach has always failed for me, and I cannot see the reason for this, or where the problem is originating. If someone can see it, and could point it out to me, I would be extremely grateful. Also, maybe if, as Thomas suggested, super wasn't on the build path, then GWT won't freak out. But then, as Thomas said, you don't get the IDE's help with these classes. I'll have to try this and see if it makes a difference, but I'd really like to understand why the above approach is failing. Thanks, Jake --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
