Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Won't Fix
-
1.0
-
None
-
Security Level: public (Regular issues)
-
None
-
Patch Available
Description
There are a some issues building Geronimo 1.0 from the src zip distribution with a clean maven repo:
1. The OpenEJB 2.0 jars have not been published, so downloads of the OpenEJB dependencies fail.
2. If you copy the OpenEJB 2.0 jars from the binary release to your local maven repo (e.g. C:\Documents and Settings\sissonj\.maven\repository\openejb\jars) you then run into another issue:
+----------------------------------------
configurations Server Configuration for the J2EE Server |
Memory: 26M/42M +---------------------------------------- |
<SNIP>
multiproject:install-callback:
[echo] Running car:install for Server Configuration for the J2EE Server
21110 [main] ERROR org.apache.geronimo.plugin.packaging.PackageBuilder - org.apache.geronimo.common.DeploymentException: org.apache
.geronimo.kernel.repository.MissingDependencyException: uri org.apache.geronimo.specs/geronimo-corba_2.3_spec/1.0/jar not found in r
epository
Where is the above dependency coming from and why isn't it in the repo?
The geronimo-service.xml file in the openejb-core-2.0 jar file has the dependency:
<dep:dependency>
<dep:groupId>geronimo-spec</dep:groupId>
<dep:artifactId>geronimo-spec-corba</dep:artifactId>
<dep:version>2.3-rc4</dep:version>
</dep:dependency>
Note that the above dependency is using the old group id of "geronimo-spec" instead of "org.apache.geronimo.specs" (needs to be fixed) and is also using a release candidate jar.
My maven local repository doesn't contain the "geronimo-spec" group id, but it does contain the "org.apache.geronimo.specs" groupid, but the geronimo-corba_2.3_spec-1.0.jar wasn't in there (wasn't downloaded).
Any ideas what is happening here and whether we can provide a workaround for those users who have downloaded the src zip to allow them to build?