On 09/13/2009 08:39 AM, PJ Gray wrote: > Thanks for the help. I messed around with it a bit more, and just kept > getting frustrated. Uggg, just isn't this hard if I want a > non-integrated solution in XCode....why is it here? Anyway, I settled > on just zipping up my whole folder and putting the zip in source > control. Big hammer solution, I know...but whatever, I was wasting too > much time figuring out stuff that should 'just work'. > > When I get some free cycles I'll take my questions to an Eclipse related > forum and maybe make some progress. > > thanks again! (just got twitter oauth working in my GWT app last > night! woohoo!!!)
By way of thanks, would you please post some code? > > -pj > > > > On Sat, Sep 12, 2009 at 3:33 PM, Jeff Chimene <jchim...@gmail.com > <mailto:jchim...@gmail.com>> wrote: > > > On 09/12/2009 10:41 AM, PJ Gray wrote: > > So maybe I am not fully understanding the versioning situation. > > > > I did some research last night, and attempted to get my project under > > source control, without any luck. It appears to me that I am > required > > to use Subclipse as my subversion client because of some special way > > that Eclipse handles projects? > > I don't think so. I think Subclipse is popular because it's a good > Subversion client. However, there may be other Eclipse Subversion > clients. > > > If that is the case, then I suppose > > I'll take my question to an Eclipse-specific forum. > > However, it seems like I should be able to use whatever client I want! > > Probably not in the way that I think you mean that statement. Eclipse > SVN clients are designed to integrate into the Eclipse environment. It's > not really a matter of bolting-on any SVN client. IDE users expect the > functional bar to be set higher than that. I have to admit that I don't > know Versions, but even if it is a GUI, and there is no Eclipse plugin, > it's only going to work as an external to Eclipse. If you reeeeely want > to stick with Versions, you'll have to figure out why Eclipse lost its > mind when the source went into SVN. > > > However, when I would add things mentioned in these emails to source > > control on my desktop, then checkout on my laptop, the GWT project was > > no longer listed in the Eclipse workspace. Even when I added > everything > > in the hidden folders to source control, it still wasn't listed in the > > workspace. I couldn't find the "special sauce" that told Eclipse that > > my project was part of the workspace, and how it was configured. > > Just to be clear: you ADDed the source of an existing Eclipse project to > Subversion via Versions? I'm guessing that somehow that shifted the > project contents underneath Eclipse, and it got confused. But, I can't > really tell from this description. It sounds like the next step is to > get a working Eclipse project back. I'd checkout the SVN source and then > import it as an existing project (since you added the Eclipse .project > and .settings/ to SVN) > > You're right, this is not a GWT-related topic. > > You have to tell Eclipse where to find your SVN repository. > > To do that, you'll have to install an Eclipse SVN plugin. If you don't > want to do that, you'll have to manage your repository outside Eclipse, > and figure out why Eclipse lost the project after adding that project to > the repository. > > If you decide to use Subclipse, be sure to understand that to get the > best performance, you must install the JavaHL library. The Subclipse > client will work w/o JavaHL, but it will lack some features. The > Subclipse wiki goes into detail about that issue. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
