MyEclipse 构建器和 CI
我正在获得对当前使用 MyEclipse 构建的项目的支持，该项目拥有规模相当大的开发团队，并且一直在没有任何 CI 流程的情况下工作。
据我所知，MyEclipse 人员 没有看到能够在 Eclipse 平台之外构建的任何价值，这对我来说毫无意义。 当您必须将来自多个开发环境的更改集成到代码库中时，持续集成非常有用，并且当您与 GUI 绑定时，自动化构建非常困难。
是否有人围绕 MyEclipse 风格的项目集设置了持续集成流程？ 如果是这样，您使用什么策略来实现它？
AFAIKT 没有 OOTB 功能可以从 MyEclipse 生成 Ant 脚本（或等效的无头构建脚本），也没有公开的方法从构建脚本平台调用 MyEclipse 构建器。
这会让我相信我需要根据 MyEclipse 生成的内容对脚本进行逆向工程，但我宁愿不必这样做。
我并不特别关心 Maven 风格的解决方案来满足我的需求，但如果您知道一个，我想听听。 从我最初的研究来看，Maven/MyEclipse 集成看起来更糟糕。
I'm picking up support on a project that is currently built with MyEclipse and has a decent sized development team that has been working without any CI processes.
From what I can tell, the MyEclipse folks don't see any value in being able to build outside of the Eclipse platform, which makes no sense at all to me. Continuous Integration is extremely helpful when you have to integrate changes into a codebase from more than one development environment, and it's pretty tough to automate builds when you're tied to a GUI.
Does anyone have continuous integration processes set up around MyEclipse style project-sets? If so, what strategy did you use to accomplish it?
AFAIKT there is no OOTB feature that can generate an Ant script (or equivalent headless-build script) from MyEclipse, nor is there an exposed way to invoke MyEclipse builders from a build-script platform.
This would lead me to believe that I'll need to reverse engineer the scripts based on what MyEclipse generates, which I'd rather not have to do.
I'm not particularly concerned with a Maven-style solution for my needs, but if you know of one I'd like to hear about it. From my initial research it looks like Maven/MyEclipse integration is even worse.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这与我使用 websphere 5.1 应用程序时遇到的问题非常相似，该应用程序只能从运行在构建机器上的 WSAD6 构建，而构建机器是从公司 IT 部门的磁盘映像构建的。 WSAD 确实有无头模式。 让 Hudson 发挥作用真的很痛苦。
如果您使用的每个构建器都有一个 Maven 插件和/或 Ant 任务，我不会感到惊讶。 我会从那里开始。
This is remarkably similar to the problems I had working with a websphere 5.1 application that could only be built from WSAD6 running on build machine built from a disk image from the company IT dept. WSAD did have a headless mode. It was a real pain to get that working from Hudson.
I would not be surprised if there was a Maven plugin and/or Ant task for each of the builders you are using. I would start there.
这是一个基于 Maven 的解决方案，所以对您来说可能有点偏离主题。
在我们公司，我们使用 MyEclipse 作为 IDE，使用 Hudson 和 Team City 进行持续集成。 这些项目基于 Maven，因此 Hudson 和 TC 可以使用它们。
当你想在 Eclipse 中打开项目时，你必须检查源代码，使用
mvn eclispse:add-maven-repo设置 Eclipse 的 Maven 存储库路径，使用mvn install< 构建它们/code> 然后运行 targetmvn eclipse:eclipse，这会根据 maven 的 POM 配置创建 Eclipse 项目设置。 然后就可以将项目导入 Eclipse 并无缝使用它。更多信息可以在 maven-eclipse-plugin 项目页面
..无缝地直到您更改 POM 配置中的某些内容 - 然后您必须再次运行
mvn eclipse:eclipse并拥有 eclipse 项目根据新的 POM 重新创建配置.. 重要的是不要忘记这一步，除非 IDE 中的项目无法正常工作并且您会想知道为什么；）我个人认为这个解决方案不是最好的，但是这就是 Eclipse 人们使用 Maven 的方式：/
希望这至少能启发你:)
Here is a Maven based solution so maybee a bit off topic for you..
In our company, we use MyEclipse as IDE and Hudson and Team City for continuous integration. The projects are Maven based, so Hudson and TC can work with them.
When you want to open the project in Eclipse, you have to check out the sources, setup maven repository path for eclipse with
mvn eclispse:add-maven-repo, build them withmvn installand then run targetmvn eclipse:eclipse, which creates the Eclipse project setup from the maven's POM configuration. Then it is possible to import the project into Eclipse and work with it seamlessly..More information can be found on maven-eclipse-plugin project page
..seamlessly until you change something in the POM configuration - then you have to run the
mvn eclipse:eclipseagain and have the eclipse project configuration recreated acording to the new POM.. it's important not to forget about this step, unless your project in the IDE won't work properly and you'll be wondering why ;)Me personally don't find this solution the best, but that's the way how Eclipse folks work with Maven :/
Hope this should inspire you at least :)
这也是我非常不喜欢 Eclipse 的另一个原因。 事实上，IDE 可以迫使您放弃被认为是最佳实践的东西，这是可耻的。
“AFAIKT 没有 OOTB 功能可以从 MyEclipse 生成 Ant 脚本（或等效的无头构建脚本）” - 我不确定我是否理解为什么这是一个问题。 可以在一两个小时内编写一个简单的 Ant build.xml，它可以完成大多数打包为 WAR 文件的 Java EE 应用程序的工作。 我不知道您是否使用 EJB，但即使添加应用程序服务器特定的任务（例如 EJB 和 JSP 编译）也不会是太大的挑战。 如果您可以就通用目录结构达成一致，它甚至可以跨项目重用。
有了 Ant build.xml，您应该能够通过签入 Subversion 来驱动 CI 流程。 我听说 Eclipse 插件可以很好地完成这项工作。
如果确实有问题，我推荐 IntelliJ。 它与基于 Cruise Control 或 Hudson 或 Jet Brains 自己的 Team City 的 CI 配合得很好。 成本并不过分，而且很快就能收回成本。
如果我误解了你的问题，我深表歉意。 但如果我做对了，我就不可能让 IDE 以这种方式向团队发号施令。
This is another reason why I intensely dislike Eclipse. The fact that an IDE can force you away from something that's acknowledged to be a best practice is shameful.
"AFAIKT there is no OOTB feature that can generate an Ant script (or equivalent headless-build script) from MyEclipse" - I'm not sure I understand why this is a problem. It's possible to write a simple Ant build.xml in an hour or two that would do the job for most Java EE apps packaged as WAR files. I don't know if you're using EJBs, but even adding app server specific tasks such as EJB and JSP compilation wouldn't be much of a challenge. If you can agree on a common directory structure it would even be reusable across projects.
With that Ant build.xml in hand, you should be able to drive your CI process simply by checking into Subversion. The Eclipse plug-ins to do that work well, I hear.
If it's really a problem, I'd recommend IntelliJ. It works nicely with CI based on either Cruise Control or Hudson or Jet Brains' own Team City. The cost isn't excessive, and it'll pay for itself quickly.
If I'm misreading your question, I apologize. But if I've got it right, there's no way I'd let the IDE dictate to the team this way.