Jeffery, I would recommend against it. It forces me to import your project into my workspace, versus having a new project that I can import cleanly from SVN. When I imported your code, it had about 30 errors I had to hunt and peck to find (these were just compiler errors, dealing with having a different SDK version). Once I set my compiler options to what they are supposed to be on my machine, the errors cleared up and everything was fine.
-Nick On Fri, Apr 6, 2012 at 8:56 PM, Jeffry Houser <jef...@dot-com-it.com> wrote: > On 4/6/2012 8:15 PM, Omar Gonzalez wrote: > >> >> >> I would of course, suspect Eclipse to lock it's workspace >> settings files. By the way, just asking - why do you want to >> commit it? >> >> >> I have no idea what the "Apache" way is regarding this. But, >> checking in the Flash Builder /Eclipse project files will make it >> insanely easy for anyone--who uses Flash Builder--to share the >> project. They just "import projects from another workspace" and >> it works. It's much easier than creating a new project. >> >> >> While this may be convenient for some Flash Builder users it leaves >> useless files behind for people that don't use Flash Builder. I think those >> shouldn't be committed but I think in whiteboards that can be up to the >> whiteboard area 'owner' so to speak. >> > > I would not want to see anything like that in a formal releases. But I > view it as a "helper" for people diving into the whiteboard stuff. > I'm not sure it's a good idea; but decided to try it anyway. And we can > re-evaluate if needed. > > > -- > Jeffry Houser > Technical Entrepreneur > 203-379-0773 > -- > http://www.flextras.com?c=104 > UI Flex Components: Tested! Supported! Ready! > -- > http://www.theflexshow.com > http://www.jeffryhouser.com > http://www.asktheflexpert.com > -- > Part of the DotComIt Brain Trust > >
