On Fri, Apr 16, 2010 at 9:35 AM, Brian Smith <[email protected]> wrote: > Hi John > Is there a reason you're using link source over putting projects onto build > paths?
Yes, Jason mentioned that method. > Here's what I would do: > Create three projects. > Put the widget you want to use in project A and project B into project C. > Set the build path of both project A & B to include project C > (properties->java build path->projects tab->add) > The widget should now to be available in A&B. > I wouldn't put B on A's build path unless you want everything, and I > wouldn't use link source (I'm not even sure there's a use case for link > source since it ought to always be in a SCM repo). For the purpose of this exercise, can we stay with the two-project approach? I don't mind having "everything" in B available to A, for the time being. And two projects gives me less things to screw up than three. Ok, I did what you suggested (include TestB on the Project page), and it did take care of all apparent errors instantly. When I try to run, however, I get: No source code is available for type com.axxessible.testb.client.NewDialog; did you forget to inherit a required module? So I tried to add: <inherits name='com.axxessible.testb.client.TestB'/> to the TestA.gwt.xml file, but when you hit the Compile button it doesn't like that at all. Did I miss a step? John -- 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.
