[ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]
David Blevins closed GERONIMO-1449:
-----------------------------------
Fix Version: (was: 1.0.1)
(was: 1.1)
Resolution: Fixed
Couple things here. The OpenEJB 2.0 jars that are from the Geronimo 1.0
release were published to the codehaus repo on the 16th and reached ibiblio on
the 17th. Building Geronimo with the published source is totally fine and
works great.
I just downloaded it and built it with no issues:
$ wget http://www.apache.org/dist/geronimo/1.0/geronimo-1.0-src.tar.gz
$ tar xzvf geronimo-1.0-src.tar.gz
$ cd geronimo-1.0-src
$ maven -Dmaven.test.skip=true new
Do not use the "m:co" or "m:checkout" goals as those are only for convenience
and result in you NOT building against the above official openejb jars. You
will instead be building against the openejb 2.0.x maintenance branch which is
now or should be 2.0.1-SNAPSHOT and is updated to work with the Geronimo
1.0.1-SNAPSHOT branch.
If you really need to rebuild OpenEJB from the 2.0 source, the correct cvs tag
to use is v2_0_0.
I'm closing this issue as "Fixed" as the openejb 2.0 jars simply needed to be
published. The patch however is against code for the future OpenEJB 2.0.1 and
does not apply to building the Geronimo 1.0 source zips and tars.
> Cannot build from Geronimo 1.0 src zip - issues with missing dependencies
> -------------------------------------------------------------------------
>
> Key: GERONIMO-1449
> URL: http://issues.apache.org/jira/browse/GERONIMO-1449
> Project: Geronimo
> Type: Bug
> Components: buildsystem
> Versions: 1.0
> Reporter: John Sisson
> Assignee: David Blevins
> Priority: Blocker
> Attachments: Geronimo-1449.patch
>
> 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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
