IvyDE + WTP：如何通过WTP忽略ivy库？ [英] IvyDE + WTP: How to workaround that ivy library is ignored by WTP?
问题描述
我发现IvyDE允许我解决一个存在冻结核心版本的Web应用程序的突出问题，需要从更新库中引入额外的代码，因此它位于Web应用程序的类路径上。为了发展速度，我发现解决工作区工具允许Eclipse将更新库项目的文件夹直接放在冻结核心Web应用程序的构建路径上。对于正常的Java应用程序，可以很好的工作。
然而，对于Web应用程序，似乎WTP（Eclipse Java EE模块）不部署类路径上由ivy库表示的文件夹。这是非常不方便的。 IvyDE开发人员认为这是一个WTP的缺点，不会修复它。我不能完全了解WTP的人对此的看法（除了它显然是复杂的），除了它们不会解决它。
所以问题是： p>
是否有合理的方式与IvyDE合作，购买我能够使用未冻结的更新库项目来维护一个冻结的webapp，最好使用Resolve in Workspace工具？
我们目前使用GlassFish 3.0.1作为网络容器。
编辑：JIRA问题是 https://issues.apache.org/jira / browse / IVYDE-227
编辑：经过一些实验，我们发现Maven对我们来说很好，并切换到这一点。原因之一是，现代日食中的Maven工具具有更好的WTP支持，并且很好地映射到我们的工作流程。
这种事情，我们只需在Eclipse项目中添加一个基于Ant的Builder，监视依赖关系文件，直接更新WEB-INF / lib并调用工作区刷新。这样我们就没有绑定到一个特定的插件，它在构建服务器上也是很好的，没有任何变化。
I have found IvyDE which allows me to solve an outstanding problem of having a frozen core version of a web application, which needs to be able to pull in extra code from an update library so it is on the classpath of the web application. For development speed I've found that the "Resolve in Workspace" facility allows Eclipse to put the folders of the update library project directly on the build path of the frozen core web application. Works well for normal Java applications.
For Web Applications, however, it seems that WTP (the Eclipse Java EE module) does not deploy the folders denoted by the ivy library on the classpath. This is very inconvenient. The IvyDE developers consider this to be a WTP shortcoming and will not fix it. I cannot fully understand what the WTP folks say about this (except that it is apparently complicated) except that they will not fix it yet.
So the question is:
Is there a reasonable way of working with IvyDE that buys me the ability to maintain a frozen webapp with an unfrozen update library project, preferrably using the Resolve in Workspace facility?
We currently use GlassFish 3.0.1 as the web container.
EDIT: The JIRA issue is https://issues.apache.org/jira/browse/IVYDE-227
EDIT: After some experimentation we found that Maven works well for us, and have switched to that. One of the reasons is that the Maven tooling in modern Eclipses have much better WTP support and maps well to our workflow.
For that kind of things, we simply add an Ant based Builder in the Eclipse project, monitoring the dependencies files, which simply updates WEB-INF/lib directly and calls for a workspace refresh. This way we are not tied to a specific plugin, and it's working great on the build server as well without any changes.
这篇关于IvyDE + WTP：如何通过WTP忽略ivy库？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
