Actionscript 3.0 cross-project folder/package structure best practise

I'm currently looking at structuring my teams projects into a consistent manner that properly utilises packages and is easily version-controlled (via SVN).

I'm interested in any 'best practise'开发者_运维技巧 with regards to project structuring and how to use consistent packaging without lumping everything into a gigantic com.domainname.projects folder structure whilst maintaining that package structure. I'm also keen to use the src/bin/lib folder structure within each project.

I guess I'm asking 'how do you do it?' and 'why?'. Sorry if this is a bit abstract for Stack Overflow but you guys give the best answers I've found.

You might need to provide more information for a "complete" answer, like your shop size, number of active projects, how you build them, and how you reuse code.

Here are some insights anyway... hope I understood the direction of you question :)

If your projects are coupled and you release new versions of each reusable artifact frequently, a single svn repo keeping a folder for each should do it. Tag/branches should remain at the project level.

Having separate repos for code that is linked may become a maintainability headache.

Package1
    src\com\domainname\Package1
        source files
Package2
    src\com\domainname\Package2
        source files
Package3
    src\com\domainname\Package3
        source files
Lib
    All packages export swcs into this folder

Problem with re-usability is going backwards -- sometimes changing something in the corelib will break all sorts of stuff going backwards, so I suggest doing running builds against it to create one large swc with all the packages in it.

I don't know why you're keen to use the bin\lib folder -- it makes more sense to have them point at things explicity rather than having parent projects export into children ...