Google 代码 SVN 使用建议

发布于 2024-08-24 07:21:50 字数 786 浏览 9 评论 0原文

我们一直在使用 Google Code SVN 来存储一个学校项目。当我们尝试不同的想法时，我们创建了新的 Visual Studio 项目并将它们存储在那里。现在我们想将所有不同的想法合并到一个最终项目中。

这是存储库的当前布局：

- svn
 - branches
    - Idea1
    - Idea2
 - tags
 - trunk
    - Sub-Project1
      - files (...)
    - Sub-Project2
      - files (...)
    - Sub-Project3
      - files (...)

我将 AnkhSVN 与 Visual Studio 一起使用，我注意到的一件事是，每次我签出其中一个项目时，其他所有项目也会被签出（当我通过 Windows 查看它时，我可以看到这一点）探险家）。

现在我们想要制作最终版本，我想知道我放置最终项目的正确方法是什么。

编辑

我认为我上面的解释做得不好。所以我又来了。

谷歌代码 SVN 存储库是否设置为单个项目？或者我可以将它们用于多个子项目吗？我问这个的原因是空的谷歌代码项目中的SVN文件结构已经是：

- svn
 - branches
 - tags
 - trunk

但我认为每个子项目都需要这三个组件。

可能是我之前不清楚，我在上面的清单中重命名了主干的部分（子项目）。每个子项目都有一个独特的目标。问题是我现在想将子项目合并成一个更大的项目。

原文

We have been using Google Code SVN to store a school project. As we were experimenting with different ideas, we created new Visual Studio Projects and stored them there. Now we want to merge all the different ideas into one final project.

Here is the current layout of the repository:

- svn
 - branches
    - Idea1
    - Idea2
 - tags
 - trunk
    - Sub-Project1
      - files (...)
    - Sub-Project2
      - files (...)
    - Sub-Project3
      - files (...)

I use AnkhSVN along with Visual Studio, one thing I noticed is that everytime I checkout one of the projects, every other project gets checked out too (I can see this when I look at it through windows explorer).

Now that we want to make the final version, I was wondering what is the correct way for me to place the final project.

EDIT

I don't think I did a good job explaining above. So here I go again.

Are google code SVN repositories set up to be for a single project? Or can I use them for multiple sub-projects? The reason I ask this is the SVN file structure in an empty google code project is already:

- svn
 - branches
 - tags
 - trunk

But I would think each sub-project would need these three components.

May be I was not clear before, I have renamed the parts of the trunk (to sub-project) in the above listing. Each sub-project has a unique goal. The thing is I want to combine the sub-projects into a bigger project now.

分享到QQ

分享到微博

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

发布评论

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

彻夜缠绵 2024-08-31 07:21:50

我要做的就是重新组织这样的东西：

/svn
    /Sub-Project1
        /branches
        /tags
        /trunk
    /Sub-Project2
        /branches
        /tags
        /trunk
    ...

你可以用简单的 svn 移动来完成所有这些。如果您当前的分支 Idea1 和 Idea2 属于当前的 über-trunk，那么我可能会将它们移动到顶级 /oldtrunk/branches 中。或者，如果它们不活动，则将其删除！这是 svn，他们仍然会在那里。 :)

接下来，您提到想要“合并子项目”，其中每个子项目“都有一个独特的目标”。如果您想继续将它们作为完全封装的子项目进行维护，我建议让它们单独构建并将它们组合为库，而不是组合源代码。在Java中，我会使用像 Ivy 这样的依赖管理工具来处理这个问题，但我不确定是什么最好的解决方案是 Google Code + Visual Studio。您可以将 Ivy 用于非 Java 的东西，但它不是那么直观。

What I would do is reorganize stuff like so:

/svn
    /Sub-Project1
        /branches
        /tags
        /trunk
    /Sub-Project2
        /branches
        /tags
        /trunk
    ...

You can do all this with simple svn moves. If your current branches Idea1 and Idea2 are of the current über-trunk then I might move those into a top-level /oldtrunk/branches. Or just delete them if they're inactive! It's svn, they'll still be there. :)

Next, you mention wanting to "combine the sub-projects" where each "has a unique goal". If you want to continue to maintain them as fully encapsulated sub-projects, I would suggest getting them to build individually and combining them as libraries rather than combining the source. In Java I would use a dependency management tool like Ivy to handle this but I'm not sure what the best solution would be for Google Code + Visual Studio. You can use Ivy for non-Java stuff but it's not as intuitive.

回复收藏 0 原文