加快 PDE 编辑-编译-调试周期
关于运行和测试 Eclipse 插件（在 PDE 内）的更有效方法，是否有任何容易实现的成果？除了精简 Eclipse 配置之外，这已经完成了。
Are there any low-hanging fruit regarding some more efficient way to run and test Eclipse-plugins (within the PDE)? Besides slimming down the Eclipse-configuration, which has already been done.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我通常会最小化启动配置本身（不确定这是否是您正在做的事情）。我是这样做的：
现在，这可能在第一次拍摄中不起作用。这可能意味着您定义的依赖项存在问题。这也是一个很好的测试。修复它，重新启动，它应该运行得更顺畅。
I usually minimize my launch configuration itself (not sure if that is what you are doing). Here's how I do it:
Now, this might not work in the first shot. This probably means you have an issue with the defined dependencies. This is also a good test for that as well. Fix it, relaunch, and it should run much smoother.
我使用 Launch As: Eclipse Application，我不认为它太糟糕。我发现更改plugin.xml（或fragment.xml）总是需要您退出并重新生成以获取更改，但更改Java并不总是如此，因为更改通常可以热交换。（PDE是善于在无法做到的时候警告你。）
I use Launch As: Eclipse Application and I don't find it to be too bad. I've found that changing the plugin.xml (or fragment.xml) always requires you to quit and respawn to pick up the changes, but changing Java doesn't always as the changes can often be hot-swapped in. (PDE is good at warning you when it can't.)
我希望 Eclipse 能够将我的插件动态插入到运行环境中——它可以使用常规插件来做到这一点。至于加快编辑-编译-调试周期，我通常在小型 SWT / Swing 应用程序中对我的工作进行原型设计，然后将它们集成到完整的产品中，但这在很多情况下可能行不通。
I'd like it if Eclipse could dynamically insert my plug-ins into the running environment -- it can do this with regular plug-ins. As for speeding up the edit-compile-debug cycle, I normally prototype my work in small SWT / Swing applications before integrating them into the full product, but this might not work in a lot of cases.