incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omar Gonzalez <>
Subject Re: Generic I/O Error When Committing to Whiteboard
Date Sat, 07 Apr 2012 08:15:01 GMT
> Perhaps having some other way of  generating an build ant build script
> from the FB project file would be useful?
I don't see exactly how as the same issues persist, mainly that not
everyone keeps their SDKs in the same place so path fixing etc will still
have to happen.

It's just a cleaner repository and a better practice to keep
project/workspace files out of source control. It's called source control
because it manages source versioning, not project settings for a particular
IDE control. This gives anyone that downloads the source files a clean set
of only the source files needed to build the project/library, how its built
can then be determined by each developer, i.e. I want to edit/build the
source with IntelliJ. Any files that are auto-generated by an IDE should
just never go in the code repository. They're always problematic.

Take for instance the test runners created by Flash Builder. If you happen
to be running only a sub set of your test cases then the test runner
application gets edited and the next person that gets updates now has a
test runner that is running different tests than they were running before
the update. That's just another example I thought of that I've seen happen.

That said I was just kind of recommending it, but I think we should all be
free to do whatever we want in our whiteboard areas. I just think its
annoying when I find Eclipse/IntelliJ/whatever files in code repositories.

This Yahoo Answers sums it up best:

We are working in teams, pretty much that's why they shouldn't be committed.


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