I found IvyDE that allows me to solve the unresolved problem of having a frozen main version of the web application, which should be able to extract additional code from the update library, so that it is on the way to the web application classes. For development speed, I found that the tool " Allow in workspace "allows Eclipse to place update library project folders directly on the build path of a frozen main web application. Works well for regular Java applications.
However, for web applications, it seems that WTP (Eclipse EE) does not expand the folders indicated by the ivy library in the classpath. It is very uncomfortable. IvyDE developers consider this a drawback of WTP and will not fix it. I cannot fully understand what the WTP people are talking about (except that it seems to be difficult), except that they still don't fix it.
So the question is:
Is there any reasonable way to work with IvyDE that buys me the opportunity to maintain a frozen website with a non-freezing update library project, is it preferable to use the Resolve in Workspace tool?
We are currently using GlassFish 3.0.1 as a web container.
EDIT: JIRA issue https://issues.apache.org/jira/browse/IVYDE-227
EDIT: , Maven . , Maven Eclipses WTP .