Comments on: Sharing Flex Projects

By: Briley

Briley — Thu, 14 Aug 2008 20:24:42 +0000

I found a really well-written resource about setting up the property files to work well with multiple developers:

http://corlan.org/2008/06/23/flex-air-projects-and-source-control/

By: Tim

Tim — Fri, 03 Aug 2007 03:30:00 +0000

We have lots of projects we share among everyone in our developer group and we check in the Eclipse files as well. I don’t think we’ve run into any major problems at all. From time to time I notice that various developer’s Eclipse installations will change the order of items within a property file but other than that its been ok.

By: Beadle Fox

Beadle Fox — Fri, 03 Aug 2007 00:13:00 +0000

Someone has to be the disenting voice, so it might as well be me

We do check in the .project, .actionScriptProperties and the .flexProperties files. I’ll stop short of saying that there is nothing developer-specific in those files, but our 5+me team hasn’t seen anything. For example, the .flexProperties file is a 1-liner for us. We have a main app, then we write many different ’s for each sub-system. Each module has its own CLASSPATH- the purpose of the .actionScriptProperties. With just a little knowledge of Eclipse it is a walk in the park to configure a variable for your pathing. As a result, each developer has their projects checked out to different locations, some on different drives. Yet we all work successfully with svn controlled versions of these files because we let Eclipse manage the connection.

Conceptually, it is no different the J2EE’s deployment descriptors. The deployer is responsible for the final linking of the pieces and parts, e.g. database pools, etc. to the web app. In this case, it is the developer who links the variable to their unique infrastructure.

To see my blog posting on how we configure eclipse, check out http://flexguy.blogspot.com/.

Beadle Fox

By: Marc

Marc — Thu, 26 Jul 2007 18:06:00 +0000

Glad to hear others do it similarly.

For our “main” mxml application, we just have a single component in it that is in our source tree. Accomplishes what Srivello said but with composition instead of inheritance.

By: Srivello

Srivello — Thu, 26 Jul 2007 17:56:00 +0000

Hi. I am so glad to read your post. I have felt your EXACT pain on an enterprise project earlier this year.

I know do what you do, a project per developer with a main application file, outside of version control.

What I recommend is to have that main application file extend a class in your source control'd that you all share, so there is little in the actual main application file that requires updating per-person manually.

Then you can

By: JesterXL

JesterXL — Thu, 26 Jul 2007 17:54:00 +0000

Same as you. You check in:

1. code (aka src directory)
2. libraries (aka lib directory)
3. assets (aka src/assets) directory (flash, images, css, etc.)

We do not check in:

1. the . property files; these are specific to the Flex project and the box they are running on
2. the bin directory
3. the html-template directory

Now, lately, we've been checking in html-template directory as more and more projects become "our Flex app in other's sites". This, combined with ANT scripts allows us to have multiple HTML views to our Flex app.