incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Campos <jonbcam...@gmail.com>
Subject Re: Generic I/O Error When Committing to Whiteboard
Date Sat, 07 Apr 2012 14:21:00 GMT
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
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message