version control - Organizing a project that uses multiple languages? -
I am currently working on a project that is perl, .net, C / C ++, and Java Is the component. These components are related to the difference, but not connected to the same release schedule. Due to the very different build / test environment requirements, it is a little burden on all those same / bin / src / lib / etc / hierarchy.
What are some good organizational hierarchies to use in it? What is the source control on dealing with this nature's project? I am currently leaning towards each language which is its branch:
repo / project 1 / pearl / main /...
repo / project 1 / .NET / main / ...
repo / project 1 / java / main /...
If you have an adherent hierarchy changing then do they have a binding release schedule Are you
I think what you have placed on the line is if you project completely with all the components If you are releasing each component separately to release it, then I can use svn: externals for different repositories or completely different repositories, then just the latest compatible of any component Tagged release. Or if you use git, use submodules to do a lot of things, external java / repo / project 1 / component / java / trunk / tags / branches / perl / trunk / tags / branches / / Component / Java - Other integration code or what you have - Tags / Branches / Components / Net / Trunk / Tags / Branches /
The exact structure depends on the workflow and how exactly the components are consolidated But you get this idea.
Comments
Post a Comment