"maven rebuild" got me past the Connector module test failure problem.
Now encountering the compile problem we had yesterday where package
org.openejb.client.naming does not exist. Deleting
openejb-core-2.0-SNAPSHOT.jar from the Maven repository and then running
"maven -Dmodules=client-builder" didn't help. Must be the case that an
additional jar file added yesterday by Dain is not yet reflected in the
repository or defined to be a dependency.
/home/craigj/geronimo/modules/client-builder/src/java/org/apache/geronimo/client/builder/AppClientModuleBuilder.java:74:
package org.openejb.client.naming does not exist
import org.openejb.client.naming.RemoteEJBObjectFactory;
Tried downloading latest release of openejb (0.9.2) from openejb.org,
but none of the jar files include the org.openejb.client.naming
package. I don't see an openejb2 in their cvs repository.
Cheers,
Craig
David Jencks wrote:
> I ran into this last night and solved it by doing a rebuild of (IIRC)
> the connector module. Certainly a complete rebuild should fix it. I
> think the EARContext interface changed in a minor way and the
> dependency tracking in maven wasn't quite enough to trigger an
> automatic recompile.
>
> Please speak up if a rebuild doesn't fix this for you!
>
> thanks
> david jencks
>
>
|