Actionscript 3.0跨项目文件夹/包结构最佳实践
我目前正在考虑以一致的方式构建我的团队项目,以正确利用包并轻松进行版本控制(通过 SVN)。
我对有关项目结构的任何“最佳实践”感兴趣,以及如何使用一致的打包,而不将所有内容都集中到巨大的 com.domainname.projects 文件夹结构中,同时维护该包结构。我还热衷于在每个项目中使用 src/bin/lib 文件夹结构。
我想我是在问“你是怎么做到的?”和“为什么?”。抱歉,如果这对 Stack Overflow 来说有点抽象,但你们给出了我找到的最好答案。
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.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
您可能需要提供更多信息才能获得“完整”答案,例如您的商店规模、活动项目的数量、如何构建它们以及如何重用代码。
无论如何,这里有一些见解......希望我理解你问题的方向:)
如果你的项目是耦合的,并且你经常发布每个可重用工件的新版本,那么一个为每个项目保留一个文件夹的 svn 存储库应该可以做到这一点。标签/分支应保留在项目级别。
为链接的代码建立单独的存储库可能会成为可维护性的难题。
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.
可重用性的问题是向后退——有时更改 corelib 中的某些内容会破坏向后退的所有内容,因此我建议对其进行运行构建,以创建一个包含其中所有包的大型 SWC。
我不知道你为什么热衷于使用 bin\lib 文件夹——让它们明确地指出事情比让父项目导出到子项目更有意义......
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 ...