> There is something wrong with how EAR modules are handled.
>
> Looking into it.
What the archetype creates is essentially identical to the already
working test case for "projects/j2ee-simple".
Diffing the structure isn't giving me any ideas.
I found in the IT test that it is adding this goal:
goals.add( "install" );
So you must run this first.
Haven't determined why yet.
I can see that the WTP component writers point to jar files - so that
may be one answer.
More investigation shows its not eclipse:eclipse's problem, it's Maven's.
Maven can't resolve the dependencies in the "ear" module but why it
can't find these in the reactor is beyond my expertise.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
