When building JEE projects with Maven (M2E), OEPE seems to ignore transitive dependencies of EAR modules.
(Before you say that OEPE doesn't support M2E) I suspect that this problem is not specific to M2E, but to the way project is packaged. If I export EAR from this example with native eclipse export facility, it's contents are OK.
EAR
`-- RAR (connector project)
|-- RAR-API (included jar)
`-- RAR-Impl (included jar)
When this EAR is prepared for deployment as exploded archive, it's 'beadep' folder contains EAR and RAR folders, transitive dependencies of RAR-API and RAR-Impl, but
not RAR-API and RAR-Impl themselves. It stays like that as long API and Impl are resolved as workspace projects (i.e. they are displayed as projects in "Maven Dependencies" library in RAR's build path). If workspace resolution is disabled, these projects turn into ordinary jars and everything starts working as expected. One drawback of this workaround is that I have to continuously update jars in local maven repository for deployed project to be in sync with it's workspace twin.
Is it possible for OEPE to handle this case gracefully somehow? Or maybe issue a warning that said projects will not be deployed and it can result in CNFE/CDNFE at runtime?
P.S. Sorry for the noise if this issue is still about M2E-OEPE interaction only. However my experiments show that non-maven connector project with described structure is handled the same way. It is possible that I misconfigured it though :)
Vadim.
Edited by: user3269289 on Aug 6, 2011 1:23 PM