Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 52825 invoked from network); 12 Jan 2006 07:11:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jan 2006 07:11:49 -0000 Received: (qmail 59438 invoked by uid 500); 12 Jan 2006 07:11:45 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 59376 invoked by uid 500); 12 Jan 2006 07:11:44 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 59363 invoked by uid 99); 12 Jan 2006 07:11:44 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2006 23:11:43 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 212E018E for ; Thu, 12 Jan 2006 08:11:22 +0100 (CET) Message-ID: <565515031.1137049881902.JavaMail.jira@ajax.apache.org> Date: Thu, 12 Jan 2006 08:11:21 +0100 (CET) From: "John Sisson (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Updated: (GERONIMO-1449) Cannot build from Geronimo 1.0 src zip - issues with missing dependencies In-Reply-To: <1628750162.1136952021939.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ] John Sisson updated GERONIMO-1449: ---------------------------------- Summary: Cannot build from Geronimo 1.0 src zip - issues with missing dependencies (was: 1.0 release installs release candidate corba spec jar file) 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 +---------------------------------------- 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: geronimo-spec geronimo-spec-corba 2.3-rc4 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? was: The 1.0 Geronimo tomcat & jetty distributions install a release candidate spec file into the old specs location : geronimo-1.0\repository\geronimo-spec\jars\geronimo-spec-corba-2.3-rc4.jar Need to determine where this is coming from. The non-RC corba spec jar is installed at the new specs location: geronimo-1.0\repository\org.apache.geronimo.specs\jars\geronimo-corba_2.3_spec-1.0.jar Priority: Blocker (was: Minor) > 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 > Priority: Blocker > Fix For: 1.0.1 > > 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 > +---------------------------------------- > > 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: > > geronimo-spec > geronimo-spec-corba > 2.3-rc4 > > 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