I had a similar question. So far i've just side stepped the issue by ignoring the folders that i dont think i need on sourcecontrol when i synch. Sounds like team > ignore is the answer.
So, um. Thanks. On Sep 11, 10:10 am, Jeff Chimene <[email protected]> wrote: > On Thu, Sep 10, 2009 at 6:32 PM, PJ Gray <[email protected]> wrote: > > > I am new to GWT and I have been using the plugin in Eclipse. I have written > > my first project, and feel confident in using the toolkit now. And I feel > > fairly comfortable using subversion (I use the awesome 'Versions' client). > > I wouldn't say I am an expert, as it always seems to 'just work' so I never > > really have to troubleshoot much. > > I don't know about "Versions". I use Subclipse, so my directions below > will have to be adjusted to fit Versions. > > > However, I am struggling trying to find documentation on how, exactly, to > > get my GWT/Eclipse project into subversion. I did a simple 'add' from the > > top level (src/war) directories. However, that imported thousands of files, > > way more than I thought should be checked in. As I looked closer, I figure > > I must need to separate out the src from the compiled javascript...that > > seems obvious. However, it is unclear what exactly in the war directory > > needs to be under source control and what is compiled or changes > > regularly. > > > I did some investigation, googling and whatnot, but I really only found > > websites complaining that with 1.6 the war directory got "polluted" and a > > few people had workarounds, but usually they either didn't work completely, > > or were using components that I wasn't. > > YMMV > > > So whats the simple answer here? I am using 1.7, is there a doc or webpage > > that explains what I should be keeping in source control? Why is there no > > "output" folder, or is that what the 'war' folder is supposed to be? > > Usually just the war/project.html and war/project.css go into version > control. As you get better with GWT, this will probably change. If > you're using server side Java, you might also have class files in the > war structure that will also go into version control. > > You've probably already figured out the team > add functionality. I > usually use team > ignore on the war/project directory to exclude the > compiled code. Everything else goes into version control. > > Everything in src/ goes into version control. > > Depending on your requirements, you might also want to include such > Eclipse files as: .project .settings/ &c > > > Any help would be appreciated, I realize this might be basic 101 stuff to > > alot of you, so I apologize if it has been answered a million times...just > > include a link with your snarky "RTFM" comment and I'll be happy! > > > -pj gray > >www.saygoodnight.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
