I generally use a vendor folder, either top-level or under src or lib that holds the submodules, and use the the --recurse-submodules option when pulling, and --recursive with git submodule update and git submodule status. I think capistrano can handle this use case decently, but I'm not familiar enough with it to know for sure.
I manage every project separetaly. Every project folder could contain all files for correct build - so all referenced files is included in "refs" directory. In this case is build easy: get latest version of "src, refs & build" directory, run the build script. The output is in "bin" directory.
The "refs" folder is consuming the disk size, but it's much simpliest than managing cross-project references with correction versions (and branches).
3rdParty-Project-A
3rdParty-Project-B
src // source code & resources
refs // referenced binaries in correct version
build // build script
bin // builded binaries & related files
deploy // files used for deploy (setup.exe, setup.msi, etc...)
... other folders ...
MyProject-A
MyProject-B
src
refs
3rdParty-Project-B // there are referenced files from 3rdParty-Project-B
MyProject-A // there are referenced files from MyProject-A
发布评论
评论（2）
我通常使用
vendor文件夹，无论是顶级还是在src或lib下保存子模块，并使用-拉取时的 -recurse-submodules选项，以及带有git submodule update和git submodule status的--recursive选项。我认为 capistrano 可以很好地处理这个用例，但我对它还不够熟悉，无法确定。I generally use a
vendorfolder, either top-level or undersrcorlibthat holds the submodules, and use the the--recurse-submodulesoption when pulling, and--recursivewithgit submodule updateandgit submodule status. I think capistrano can handle this use case decently, but I'm not familiar enough with it to know for sure.我单独管理每个项目。
每个项目文件夹都可以包含正确构建的所有文件 - 因此所有引用的文件都包含在“refs”目录中。在这种情况下，构建很容易：获取最新版本的“src、refs & build”目录，运行构建脚本。输出位于“bin”目录中。
“refs”文件夹占用磁盘大小，但它比使用更正版本（和分支）管理跨项目引用要简单得多。
I manage every project separetaly.
Every project folder could contain all files for correct build - so all referenced files is included in "refs" directory. In this case is build easy: get latest version of "src, refs & build" directory, run the build script. The output is in "bin" directory.
The "refs" folder is consuming the disk size, but it's much simpliest than managing cross-project references with correction versions (and branches).