Tim, In order to get something to work in GWT you have to have the Java source, and as far as I know you have to put a module file in the same package hierarchy with a <source path='relative.package.path' /> element. So you may as well make your project B a gwt project without any entry points anyway. I think you will find that the path='X' attribute isn't as flexible as you would like it to be. For example, I don't "think" it supports things like ".." for previous package, and I just tried and failed to get a compile to work with a module that had path="source in another project" or a single module that is defined in package com.domain.packageA with an element like <source path='com.domain.packageB />
-John On May 15, 4:45 pm, Tim McCormack <[email protected]> wrote: > On May 15, 3:00 pm, Rajeev Dayal <[email protected]> wrote: > > > Now, suppose that project B only has GWT client source in it (no RPC) - then > > the new version of the plugin will handle this case - it will automatically > > pull the dependent project's source folders onto the classpath when > > compiling or running hosted mode. > > What if B is not a GWT project, but instead a regular Java project? I > can't have it compile into A's output folder, because it won't output > GWT classes. > > That's the situation I have right now, and I can't seem to get GWT to > compile with outside libraries. How is it done? > > - Tim McCormack --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
