Kevan,
Thank you!
I'm finally past that point in the build!
Here is my JRE and environment info - maybe it will help to figure out
the problem with Xmlbeans:
I'm using Sun Java version 1.5.0_06.
JAVA_OPTS=-Xms128m -Xmx1024m
JAVA_HOME=/opt/jdk1.5.0._06
JRE_HOME not set.
Jay
Kevan Miller wrote:
Jay,
Thanks for the info. I'm not sure if it muddies the water or clears
it... The problem seems to be a problem with the Xmlbeans plugin. I
raised a jira last night-- http://jira.codehaus.org/browse/MXMLBEANS-34
It looks like the Xmlbeans plugin is adding the container pom to the
CLASSPATH of an Xmlbeans compilation phase. This causes the "error in
opening zip file" problem (and supposedly the subsequent problems).
There seems to be some JRE runtime or environmental issue that causes
this problem. Just hard to know what...
The problem can be avoided by editing the openejb server pom (i.e.
~/.m2/repository/org/apache/openejb/server/3.0-incubating-SNAPSHOT/server-3.0-incubating-SNAPSHOT.pom)
and removing the dependency on the openejb container pom as follows:
<dependencies>
<!--
This dependency is here to ensure that absolutely nothing
under the container module section can be dependent on any
server modules.
-->
<!-- <dependency> -->
<!-- <groupId>org.apache.openejb</groupId> -->
<!-- <artifactId>container</artifactId> -->
<!-- <version>${version}</version> -->
<!-- <type>pom</type> -->
<!-- <scope>compile</scope> -->
<!-- </dependency> -->
</dependencies>
This dependency is only needed by OpenEJB to detect invalid
dependencies at OpenEJB build-time. So, I'm going to see if I can work
up an exclude in Geronimo which will work around this issue...
--kevan
