有关准备已配置的 Eclipse 包以分发给开发团队的建议
我正在努力建立一个完全配置的 Eclipse 环境，并将其分发给我的团队。我想分发安装并配置了所有所需插件的 zip 包，以便在安装（解压 zip）时我们都使用相同的 IDE（即都具有相同的插件，特别是版本和配置）数据）。
我当前的问题是关于 Mylyn 插件。我希望我分发的包能够预先配置为指向我们的问题跟踪器。此配置信息包含在 .metadata 目录是否是最佳实践。一方面，这需要在安装过程中执行额外的步骤。将 Eclipse 捆绑包解压到安装目录后，用户需要将 .metadata 目录复制到其工作区。这是推荐的，还是有更好的方法？有没有办法将默认的repositories.xml文件放在Eclipse安装目录中，并让Eclipse在第一次启动时将该信息放入
是否有关于配置自定义 Eclipse 分发环境的推荐实践的管理员文档？
用户是否将 .metadata 放入版本控制存储库中并/或使用 Eclipse 安装包将其分发给用户？
I'm working on setting up a fully configured Eclipse environment that I will distribute to my team. I'd like to distribute the zip package with all of the desired plugins installed and configured so that upon installing (extracting the zip) we are all using the same IDE (i.e. all have the same plugins, esp with regard to versions, and configuration data).
My current question is regarding the Mylyn plugin. I'd like the package I distribute to be pre-configured to point to our issue tracker. This configuration information is contained in <workspace>/.metadata/.mylyn/repositories.xml.zip. However, I question whether it is best practice to distribute the .metadata directory. For one thing, this will require an extra step in the installation process. After extracting the Eclipse bundle to the installation directory, the user will need to copy the .metadata directory to their workspace. Is this recommended, or is there a better way? Is there a way to put a default repositories.xml file in the Eclipse installation directory and let Eclipse put that information in <workspace>/.metadata on the first startup of Eclipse?
Is there any administrator documentation on recommended practices for configuring a customized Eclipse environment for distribution?
Are users putting .metadata in a version control repository and/or distributing it to users with an Eclipse installation package?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不确定它在多大程度上涵盖了您特定的 Mylyn 特定用例，但 Google 的 Workspace Mechanic for Eclipse 似乎值得一看：
即使不支持开箱即用，但看起来它是为了通过您自己的任务进行扩展而构建的。
I'm not sure how well it covers your particular Mylyn-specific use case, but Google's Workspace Mechanic for Eclipse seems worth a look:
Even if it's not supported out of the box, looks like it's built to be extended with your own tasks.