How to check out a project using Flex Builder 3 / Eclipse
- In FB3 Do File->New Project->SVN->Checkout Projects from SVN
- In the Select/Create? Location screen of the Checkout from SVN wizard, select Create New repository location and click 'Next'.
- For Repository URL, enter the URL listed on the Project's Download page such as: http://trac.puremvc.org/Demo_AS3_Flex_EmployeeAdmin, and click 'Next'.
- Select the tag folder for the latest release as the folder to check out such as 'tags/EmployeeAdmin_1_2', and click 'Next'.
- Select Check out as a project configured using the New Project Wizard, and click 'Finish'.
- In the New Project Wizard, choose the appropriate Project Type for the project such as Flex Builder->Flex Project, and click 'Next'.
- For Project Name, enter the project name described on the project's Installation page, such as: EmployeeAdmin. (This will create the project in your current workspace folder. To check out the project to another folder, uncheck Use Default Location and type or browse to another folder.)
- Choose Web application as the type of project and click 'Next'.
- Leave Output Folder set to 'bin' and click 'Next'.
- Click the Finish button.
- Click OK to the dialog that tells you that .project and other resource files may be overwritten, this is OK.
A this point the project will be checked out and should build successfully. If you press the green Run button, the app should come up in your default browser and work. The SVN project is already set up to ignore all the right folders and files, so you can make changes and check them back in now.
NOTE: Ignored Files in Repository
If you browse the code repository, you'll notice that the following files are ignored by SVN:
- .settings [folder]
- .actionScriptProperties
- .flexProperties
- .project
- html-template [folder]
This is because different versions of the Flex Builder IDE sometimes have difficulty processing projects created by other versions. Therefore, a developer using, the latest Flex 3 Builder release might have no luck coping with the project as originally created with a beta just a few revisions back. So, this means for multiple developers to work effectively on the project with varying IDEs, we must have SVN ignore the above files when we create the project for the first time on our machines.
