|Re: J2EE Module Dependencies and build problems [message #219081 is a reply to message #215695]
||Fri, 08 August 2008 10:25
| Steffen Neumann
Registered: July 2009
Wolfgang Knauf wrote:|
> Problem 1 sounds like
I am hit by the same problem. Just to recap:
I have a dynamic Web Project and two Java projects A and B,
and B depends on A.
I can successfully add one of the java projects "A" as
JEE module dependency, but If I add the second java project "B"
as JEE module dependency, hit "apply", it is silently dropped the next time
I open the JEE module dependency configuration.
Similarly, if I manually edit
<dependent-module deploy-path="/WEB-INF/lib" handle="module:/resource/org.metware.bigmet/org.metware.bigmet ">
and change the handle to match the second java project,
the entry is deleted again.
To me the most annoying "feature" is that without a message
even in the error log I have no clue what's going wrong.
I saw quite a few bug reports on JEE module dependency configuration,
and I am somewhat lost in which category mine falls.
What are the requirements for a java project to be a valid JEE dependency ?
What do I have (and not have) to export from the projects A and B ?
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=205004 (fixed in 2.0.2)
I have WTP 3.0.0, and supposedly the above bug was fixed
The eclipse installation seems to be current,
there are no available updates shown.
Any hints appreciated,
*** System properties:
Linux x86_64 on Ubuntu hardy
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
org.eclipse.jst (3.0.0.v200806111800-7U-8Y9LIrwYBUV7sHGjhtz0LTrMd) "J2EE Standard Tools (JST)"
org.eclipse.wst (3.0.0.v200806092130-7A-8Y8QqN2lf4VSWrI2ek5Pf4k7s) "Web Standard Tools (WST)"
Powered by FUDForum
. Page generated in 0.01980 seconds