Flex & SVN - what to ignore?

I want the version to run my Flex application with SVN. What should I include and ignore?

+7
flex svn
source share
4 answers

I ignore only the .settings directory.

You should look at the source of the project files ( .actionScriptProperties , .flexProperties , .project ) and decide whether you or your team need their settings during a clean check or not.

If you put these files in a version control, you should avoid certain directories on workstations in the settings (Flex server settings) and replace them with path variables .

This is, for example, the contents of my .flexProperties file:

 <?xml version="1.0" encoding="UTF-8" standalone="no"?> <flexProperties enableServiceManager="false" flexServerFeatures="4" flexServerType="2" serverContextRoot="/myProject" serverRoot="${HTTP_DOCS}/myProject/" serverRootURL="http://localhost/myProject" toolCompile="true" useServerFlexSDK="false" version="1"/> 
+5
source share

I agree. bin-debug and bin-release are those that are ignored.

+3
source share

IMHO you can ignore:

  • .settings
  • .FlexUnitSettings
  • html template (can be generated)
  • .actionScriptProperties
  • .flexProject
  • .project
  • .sourceMate (or any other plugin you have)
+1
source share

I actually save everything except the source code from SVN.

My SVN-related project in FB does not contain project information at all (it's just a project), I have a second project that I run locally, this is a Flex / AIR project that just references the source in my controlled project.

This not only means that I do not risk checking the files of the generated files. *. etc. This means that I can save a different setting from other members of my team.

+1
source share

All Articles