IvyDE + WTP: How to workaround that ivy library is ignored by WTP?

Question

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 JEE 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

Answer 1

Did you try to add the ivy.xml module to your project's Java EE Module Dependencies?

Answer 2

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.