单个 Subversion 存储库可以在 Eclipse 中作为多个项目进行管理吗？
我有一个帮助台应用程序，其中包含可以根据用户需要/偏好单独下载和安装的模块。 其结构与Drupal等许多软件非常相似，模块可以轻松加载/卸载。
我为此帮助台应用程序使用单个 SVN 存储库，并为每个模块创建不同的标签。 在我的 Eclipse 上，我将所有内容都作为一个项目。
- 我的问题是，单个 Subversion 存储库可以在 Eclipse 中作为多个项目进行管理吗？
- 我可以为整个应用程序同时为每个模块创建一个 Eclipse 项目吗？
- 另一个要求是，通过将每个模块拆分为不同的项目将使 Eclipse 构建速度更快。
原因是，我想将每个模块的编程工作委托给另一个人，而不需要公开所有内容。 这个人只会看到& 仅处理模块，但提交到主存储库。
我知道Eclipse每个项目都会有配置文件，会不会有冲突。
I have a Helpdesk application that contains modules that can be downloaded and installed separately as required / preferred by the users. The structure is very similar to many software such as Drupal, which modules can be loaded/unloaded easily.
I'm using a single SVN repository for this Helpdesk application and create different tags for each module. And on my Eclipse I have everything as a single project.
- My question is, can a single Subversion repository managed as multiple projects in Eclipse?
- Can I create one Eclipse project for the whole application and at the same time for each module?
- Another requirement is that by splitting each module as a different project would make Eclipse builds faster.
The reason is, I want to delegate programming work of each module to another person without the need to expose everything. The person would only see & work on the module only but commit to the main repository.
I know that Eclipse will have configuration files for every project, would there be any conflict.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我已经很好地了解了在一个存储库中存储多个 Eclipse 项目的情况。 每个项目都存储在存储库根目录下的单独文件夹中。 然后，我使用 Subclipse 将每个文件夹作为单独的 Eclipse 项目进行检查。
I've had good look storing multiple Eclipse projects in one repository. Each of the projects is stored in a separate folder under the repository's root. Then, I use Subclipse to check out each of those folders as a separate Eclipse project.
我不认为您应该嵌套 Eclipse 项目（以便主项目包含许多子项目）。
您可以将各个项目分组为 Eclipse 所谓的“团队项目集”（位于“导出/导入”菜单中），而不是主项目。 这是一个 XML 文件，定义所有项目的位置。 您也可以将该文件放入 Subversion。
因此，您将拥有该模块的所有项目以及该 XML 文件（它本身不是一个项目），全部都在 Subversion 中（可以是同一个存储库，也可以分布在多个存储库中）。
I do not think that you should nest Eclipse projects (so that a master project contains many sub-projects).
Instead of the master project, you could group the individual projects into what Eclipse calls a Team Project Set (found in the Export/Import menus). This is an XML file that defines where all the projects are. You can put that file into Subversion as well.
So, you would have all the module's projects, and that XML file (which is not a project itself), all in Subversion (could be the same repository, could be spread over several).
我不认为这绝对是可能的。 就我个人而言，我会将模块完全拆分到不同的项目中，并且我可能会使用 Eclipse 的插件结构来解决它们与主项目之间的依赖关系。 如果您将插件作为 jar 提供，它们仍然是模块化的。 然后，您可以将每个插件作为 Eclipse 中的单独项目以及 SVN 中的单独文件夹进行控制。
I don't believe this is strictly possible. Personally, I would split the modules up into different projects entirely, and I would probably use Eclipse's plugin structure to resolve dependencies between them and the main project. If you ship the plugins as jars, they're still modular. Then, you can control each plugin as a separate project in Eclipse, and a separate folder in SVN.
那完全没有问题！ 只需在 svn 存储库上创建主干/标签/分支结构即可。 创建不同的项目，然后将这些项目签入 svn 系统上的 trunc 文件夹中。 完成的！
That is no problem at all! Just create your trunk/tags/branches structure on your svn repo. Create your differen projects and then check thos projects into your trunc folder on your svn system. Finished!