如何处理依赖于同一来源的多个项目? [英] What to do with multiple projects depending on the same source?
问题描述
过去一个月我遇到过两次这种情况，我什至不确定如何将其表述为 Google 查询.
This is something I've come across twice in the past month and I'm not even certain how to phrase this as a Google query.
我实际上使用 SVN 来完成所有这些工作，但看起来这应该是一个普遍的版本控制问题.
I'm actually using SVN for all of this, but it seems like this should be a general versioning problem.
我们有两个项目，其中一个依赖于另一个的一些代码.由于 API 问题，在产品之间建立某种形式的链接是不切实际的(而且我不想必须配置所有非编码人员的机器才能使其工作).
We have two projects and one of them is dependent on some of the other's code. Due to API issues, it is not pragmatic to have some form of linkage between the products (and I don't want to have to configure all of the non-coders' machines to make this work).
我想如果我将共享代码的副本放入目录结构中，我最终会覆盖 SVN 使用的所有配置文件.这意味着依赖项目目录中的版本将无法再更新.
I would imagine that if I put a copy of the shared code into the directory structure, I will end up overwriting all of the config files that SVN uses. This would mean that the version in the dependent project's directories would no longer be able to update.
例如:
项目 #1 需要使用类 MyExampleClass，但是，MyExampleClass 是被定义为项目 #2 的一部分并被项目 #2 需要的东西.
Project #1 needs to use the class MyExampleClass, however, MyExampleClass is something which is defined as a part of and needed by Project #2.
推荐答案
这篇关于如何处理依赖于同一来源的多个项目?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
