Geek Answers Handbook

What files should go into source control in a Flex Builder project?

I noticed that Eclipse (Flex Builder) generates hundreds of metadata files. Should I check them in my original control? They seem necessary, because if I delete them, Flex Builder will simply open an empty workbench ...

Some of these files are clearly not owned by the control source (for example, .history files and some cache files). If I delete them, my project will open again without a hitch. But this list is long, and there seems to be no clear separation between folders that contain files belonging to the source and those that do not.

I can’t just put them all in svn, even if I ignored the inefficiency, because Eclipse constantly generates new ones with different names, which, in turn, is also crucial for downloading the project.

Can someone please enlighten me?

+5
source share
4 answers

Do not check hundreds of metadata files. If you want to check the project so that it can be easily imported, follow these steps:

.actionScriptProperties
.project
.flexProperties

Both "html-template" and "libs". As the Christian says, any resources you depend on. I usually support them as separate Flex library projects.

+3
source

src, src . (, Cairngorm SWC, as3corelib ..), Flash/ , , . - (bin- *), IDE- , , -, , ; , , , - FlexBuilder ( ), , mxmlc compc) - .

+1

eclipse, .project,.properties, .settings, . , URL-, .

, , - , SCM, , . I.E ant, local.properties .

+1

, .actionScriptProperties,.project .flexProperties ? URL- . ? , . , ..

0

More articles:


All Articles