Last updated on OCTOBER 10, 2014
Applies to:Oracle Enterprise Pack for Eclipse - Version 126.96.36.199.0 to 188.8.131.52.0 [Release Oracle11g]
Information in this document applies to any platform.
When building JEE projects with Maven (M2E), OEPE ignores transitive dependencies of EAR modules. This problem is not specific to M2E, but to the way project is packaged. If we export EAR from this example with native eclipse export facility, it's contents are OK.
`-- 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.The drawback of this workaround is that the developer should have to continously update jars in local maven repository for deployed project to be in sync with it's workspace twin.
Is is 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?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms