Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jonbcampos@gmail.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALorpXcpKU7LjvwMcYrTPVBW6AgtR=cwRX3hR4Q3DOnj2vAvLQ@mail.gmail.com>
References: <CBA46B62.3EC54%aharui@adobe.com>
	<4F7F2004.2030407@dot-com-it.com>
	<CAJQBtg=x=8Le2mgmaxdh=pARPSekEGvy-zPtF9raSXSaqxrmfQ@mail.gmail.com>
	<4F7F38FD.1000701@dot-com-it.com>
	<CAJQBtg=pP1O8TpG4NC_inEcS8kOP4DE3ifx1FAOy901_3v27ZA@mail.gmail.com>
	<4F7F7A95.9090602@dot-com-it.com>
	<CAEFz_vvOJBLG9jmbtgQn1prQpGKQgu56-3Bm2d778p_r5FCC4w@mail.gmail.com>
	<4F7F90CF.2060703@dot-com-it.com>
	<CALorpXfKVgAYPPt+CmUroNRbACuwvCcMiZ_+WMRnx0iHUbR=Dg@mail.gmail.com>
	<BB932B70-373B-4D87-9FCA-4F4A3C80BD4D@classsoftware.com>
	<4F801A5C.80305@dot-com-it.com>
	<CALorpXcpKU7LjvwMcYrTPVBW6AgtR=cwRX3hR4Q3DOnj2vAvLQ@mail.gmail.com>
Date: Sat, 7 Apr 2012 09:21:00 -0500
Message-ID: 
 <CAAd0WrYGSbeyw_9Ktcs79Nk_sTc5YuH4-r38-nMbfL7EqmgAAw@mail.gmail.com>
Subject: Re: Generic I/O Error When Committing to Whiteboard
From: Jonathan Campos <jonbcampos@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8f83a9097c6fd304bd177b54

--e89a8f83a9097c6fd304bd177b54
Content-Type: text/plain; charset=ISO-8859-1

Just as a "me too" I can say that not checking in the .* files is the way
to go when working in teams. There are many problems it solves. I
completely agree with nick here.
On Apr 7, 2012 8:18 AM, "Nicholas Kwiatkowski" <nicholas@spoon.as> wrote:

> Your Flex 4.6 is not the same as my Flex 4.6.  They are close, but the
> problem is I don't have an SDK compiler named "Flex 4.6.0" on my machine (I
> have "Flex 4.6.0-23043" and "Flex 4.6.0-23201").  Additionally, I also add
> certain compiler arguments to all of my projects.  By having it included,
> its workable for the initial download, but where I run into issues is for
> every time I update to head for that project (I plan on importing it via
> SVN so that I can keep up with your changes and submit patches should they
> need to be submitted), I have to go and figure out what settings you pushed
> out, and what I need to change /again/, because updating from HEAD will
> overwrite my settings files because at one time, they were versioned.
>
> If you work in a closed environment with a small team, I'm sure putting
> workspace and project files into SVN could work -- but that really isn't
> the case here.  Heck, I do it for my own SVN when I'm working on my own
> personal projects.  For these larger projects, where the expectation that
> LOTS of people are grabbing the versioned code, we should shy away from
> keeping these files in the repos.  It just makes it ugly, and could cause
> problems for those that are not as intimate with the compiler settings as
> we are.
>
> -Nick
>
> On Sat, Apr 7, 2012 at 6:43 AM, Jeffry Houser <jeffry@dot-com-it.com>
> wrote:
>
> > On 4/7/2012 3:38 AM, Justin Mclean wrote:
> >
> >> HI,
> >>
> >>  Once I set my compiler options to what they are supposed to
> >>> be on my machine, the errors cleared up and everything was fine.
> >>>
> >> I'd assume the SDK wasn't set to a version in the project but just "use
> >> default". This could also cause errors if you had a different SDK set by
> >> default and imported the code from SVN.
> >>
> >
> >  That was the first thing I checked; and it was set to use a specific SDK
> > ( Adobe Flex 4.6 ).  I've never had a situation where that setting [ff
> set]
> > was not transferred, although I do not have tons of experience with this.
> >
> >
> >
> > --
> > 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
> >
> >
>

--e89a8f83a9097c6fd304bd177b54--