Subversion svn:externals - 这里出了什么问题?

发布于 2024-08-23 21:45:50 字数 1609 浏览 3 评论 0原文

我首先想说我已经阅读了 Subversion 手册。我已阅读这个问题。我还读过这个问题< /a>.这是我的困境。

假设我有 3 个存储库,布局如下:

  • DataAccessObject/
    • 分支机构/
    • 标签/
    • 树干/
      • 数据访问对象/
      • DataAccessObjectTests/
  • PlanObject/
    • 分支机构/
    • 标签/
    • 树干/
      • 计划对象/
      • 计划对象测试/
  • WinFormsPlanViewer/
    • 分支机构/
    • 标签/
    • 树干/
      • WinFormsPlanViewer/

PlanObject 和 DataAccessObject 存储库包含共享项目。它们由 WinFormsPlanViewer 使用,但也由其他几个存储库中的其他几个项目使用。

请耐心听我说。我将 svn:externals 定义放在 WinFormsPlanViewer/trunk 文件夹上,如下所示:

https://server/svn/PlanObject/trunk Objects<br/>
https://server/svn/DataAccessObject/trunk Objects<br/>

这是我执行 svn 更新后看到的内容。

  • WinFormsPlanViewer/
    • 分支机构/
    • 标签/
    • 树干/
      • WinFormsPlanViewer/
      • 对象/
        • 数据访问对象/
        • DataAccessObjectTests/

PlanObject 的东西甚至没有在更新中出现!我不知道这是否与之有关,但 PlanObject/trunk 文件夹上也有一个外部定义:

https://server/svn/DataAccessObject/trunk Objects<br/>

这里发生了什么?我做错了什么?当 PlanObject 也使用 svn:externals 引用 DataAccessObject 时,使用 svn:externals 从 WinFormsPlanViewer 引用 PlanObject 和 DataAccessObject 是否会产生不良后果?

I first want to say I've read the Subversion manual. I've read this question. I've also read this question. Here's my dilemma.

Let's say I have 3 repositories laid out like this:

  • DataAccessObject/
    • branches/
    • tags/
    • trunk/
      • DataAccessObject/
      • DataAccessObjectTests/
  • PlanObject/
    • branches/
    • tags/
    • trunk/
      • PlanObject/
      • PlanObjectTests/
  • WinFormsPlanViewer/
    • branches/
    • tags/
    • trunk/
      • WinFormsPlanViewer/

The PlanObject and DataAccessObject repositories contain shared projects. They are used by the WinFormsPlanViewer, but also by several other projects in several other repositories.

Bear with me here. I put an svn:externals definition on the WinFormsPlanViewer/trunk folder like this:

https://server/svn/PlanObject/trunk Objects<br/>
https://server/svn/DataAccessObject/trunk Objects<br/>

And here's what I see after I do an svn update.

  • WinFormsPlanViewer/
    • branches/
    • tags/
    • trunk/
      • WinFormsPlanViewer/
      • Objects/
        • DataAccessObject/
        • DataAccessObjectTests/

The PlanObject stuff doesn't even come down in the update! I don't know if this has anything to do with it, but there's an externals definition on the PlanObject/trunk folder also:

https://server/svn/DataAccessObject/trunk Objects<br/>

What's going on here? What am I doing wrong? Are there bad consequences of referencing the PlanObject and the DataAccessObject from the WinFormsPlanViewer using svn:externals when the PlanObject references the DataAccessObject using svn:externals also?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

月下客 2024-08-30 21:45:51

您已配置 svn:externals 属性以使用两个不同 URL 的内容填充 Objects 目录。尝试创建两个具有不同目录名称的 svn:externals:

https://server/svn/PlanObject/trunk PlanObjects
https://server/svn/DataAccessObject/trunk DataAccessObjects

You have configured the svn:externals property to populate the Objects directory with the contents of two different URLs. Try creating the two svn:externals with different directory names:

https://server/svn/PlanObject/trunk PlanObjects
https://server/svn/DataAccessObject/trunk DataAccessObjects
战皆罪 2024-08-30 21:45:51

啊,今天早上刚想到这个,就想踢自己一脚,因为之前没想到。我将像这样定义我的 svn:externals :

https://server/svn/PlanObject/trunk/PlanObject 对象/PlanObject
https://server/svn/DataAccessObject/trunk/DataAccessObject 对象/DataAccessObject

我正在标记的 对象/DataAccessObject Billie 的回答被接受,因为他确实回答了我关于为什么 svn:externals 定义不起作用的问题。

Ah, just thought of this this morning and wanted to kicked myself because I didn't think of it before. I'm going to define my svn:externals like this:

https://server/svn/PlanObject/trunk/PlanObject Objects/PlanObject
https://server/svn/DataAccessObject/trunk/DataAccessObject Objects/DataAccessObject

I'm marking Billie's answer as accepted because he did answer my question about why the svn:externals definition wasn't working.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文