Thanks, that helps clarify things. Repacking the jars was on my short list of contingencies to try out. These particular jars that were causing me grief are third-party. I think I'll repack them and throw them into a local repo.
Now I'm also suspecting that I may have been having some problems with the GWT compiler (through the Google plugin) not seeing transitive dependencies resolved from ivyde. I'm going to re-try a couple of my failed attempts using a vanilla launch config. Thanks again for all the help. On Wed, Oct 6, 2010 at 10:25 PM, Chris Marks <[email protected]> wrote: > This is actually a problem in how your dependency is built. In the > dependency you are using, you need to include both the class files and the > java files in the jar. This is especially important if you are using a > build script outside of Eclipse (say in a continuous build environment). It > doesn't seem that GWT modules are well documented in the area of creation > and it took me looking at a couple modules from Google to understand that is > how things are supposed to be deployed. > > Hope this helps. > > Thanks, > topher > > [email protected]
