[ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]

Matt Hogstrom reassigned GERONIMO-1449:
---------------------------------------

    Assign To: David Blevins  (was: Matt Hogstrom)

Geronimo 1.0 was release with OpenEJB modules/core using the following spec 
jar:  geronimo-spec-corba at version 2.3_rc4.  After the release of Geronimo, 
OpenEJB had not been distributed and people could not compile the source 
distribution.  It was decided to publish the OpenEJB 2.0 release.  Prior to 
that release the spec jars were updated to geronimo-corba_2.3_spec and version 
1.0 which made them incompatible with the spec jars Geronimo had been compiled 
against.

We shouldn't be updating jars after the release.  OpenEJB 2.0 should retain the 
same jars we released with (see above).  We can debate whether a new set should 
be used for 1.1.

David B...can you recompile the OpenEJB 2.0 with the previous jars and then 
push out the modified release?

thanks

> 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
>      Fix For: 1.0.1, 1.1
>  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

Reply via email to