On Nov 3, 2009, at 12:12 PM, David Blevins wrote:
On Nov 3, 2009, at 7:27 AM, Rick McGuire wrote:
I ran into a little issue with the bundlized version of the openejb-
client jar. This jar has a Require-Bundle dependency on
org.apache.openejb.openebj-core, but the project pom does not
specify a maven dependency on openejb-core. This is causing a bit
of an issue when used in Geronimo 3.0 because the framework is
using the maven dependencies to determine the install/start order
for the different bundles we're using. Since there's no maven
dependency, the openejb-client is giving a resolution constraint
failure on the required jar depending on the relative order the
different openejb bundles get started. Having the correct maven
dependency in the pom would sort all of that out.
Is there some reason why this was done this way, or is it just an
oversight?
I'm not sure why there is a Require-Bundle dep on openejb-core.
Maybe someone else can comment on that.
Code-wise, the client jar is designed to work without any other
OpenEJB libraries or third party dependencies (except for specs), so
that explains why there is not a maven dep.
Still looking for some followup. As mentioned the openejb-client
module does not need and should not be allowed to use the code in
openejb-core. Going to remove that dependency.
-David
