I was affected by this too but found a workaround by following these instructions:
- Add the user library to the Java build path (Properties-Java Build Path-Libraries-Add Library). This will add a classpath container entry for the user library.
- Switch to the
J2EE Module Dependencies(the Java build path changes must be applied first) and select the
- A selection will be visible for the user library classpath container entry just added (will be prefixed by
(Classpath))). Select this and click
OK(the special dependency attribute will be added to the classpath entry and the value for the attribute will be the special value
../indicating that the resolved JARs should be added into the parent module at the same location as the web module).
It worked well for me, and it may even be the technically correct way with WTP. (On the other hand, who can know the mind of WTP? ;-)
Well yes this is also a workaround, another workaround is just to deploy the library separately via WTP ( I can see it as a separate module in add/remove project dialog).
However the bug is acknowledged by eclipse... so there is no really correct way with WTP 2.0.2 afaik