Hi John Is there a reason you're using link source over putting projects onto build paths?
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). Hope this helps Brian On 16 April 2010 14:12, John <[email protected]> wrote: > On Mon, Apr 12, 2010 at 11:40 AM, Jason Parekh <[email protected]> > wrote: > > As you've found, dependent projects are a very rough area in GPE. One > > solution that should work for you is: in your main project, use "Link > > Source" to add your widget project's source folders. > > Jason and Craigo, I apologize for not replying earlier. When I first > asked about mixing projects, I was at a stage where I had just broken > one of the projects that made up the larger project I was working on. > > Under the pressure of delivering some working software for the client, > I put "doing things properly" on hold. In fact, to fix the broken > project, I created a new project, and copied all the pieces, one at > time, from the broken project into the new one, and things worked. > I'm happy that it got things working, but not happy when I don't > understand what's going on, nor how to do things properly. > > Ok, in the hope that somebody is still willing to lend some advice, I > have created two projects: the most simple, trivial GWT projects that > I can make. > > STEP ONE -------------------- > Project TestA was made using the Eclipse GWT project creator, then I did: > > 1. in the src branch, delete server and shared folders > 2. delete the test and test-classes folder > 3. in the client folder, delete these classes/interfaces: > GreetingService > GreetingServiceAsync > > 4. fix errors in TestA.java until all that's left is: > > imports, plus > public class TestA implements EntryPoint { > > public void onModuleLoad() { > > Label label = new Label("hello"); > RootPanel.get("nameFieldContainer").add(label); > } > } > > 5. in the war branch, take the servlet parts out of web.xml > > 6. under Project > Properties > Java Build Path > Source tab, remove > the test part, which was deleted. > > I set the -noserver option, and run with a lampp setup. Set the > apache server to consider the war folder as a document root directory. > It works. > > STEP TWO --------------------- > Made another project, TestB, exactly the same as above > > STEP THREE ------------------- > To project TestB, I added a custom widget that I will want to use in > other projects, such as TestA. It is a simple class called NewDialog, > which extends the GWT DialogBox. > > STEP FOUR ---------------------- > Here is where I'm stuck. I can't get the "Link Source" to work. Not > only doesn't it work, it seems to behave differently depending on what > day of the week it is (if you get my drift). > > Starting with (for TestA) Project > Properties > Java Build Path > > there are tabs for Source, and Projects. The Link Source option > appears on the page with the Source tab. > > Question 1: Should I also be adding TestB to the Projects page? > > Question 2: When using Link Source, the Source page originally shows: > > TestA/src > > Then, on the Link Source dialog, if I enter: > > /home/john/workspace/TestB/src > > it says "The folder is already a source folder" > > If I specify the linked location even deeper, like: > > /home/john/workspace/TestB/src/com/axxessible/testb/client > > it says "The folder 'TestA/client' already exists." > > In each of these situations, I'm sitting there saying, "Yeah, I > know--so what!?" Obviously, I'm missing a fundamental point here. > Can you point me in the right direction? > > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
