[jira] Updated: (GERONIMO-1449) Cannot build from Geronimo 1.0 src zip - issues with missing dependencies

2006-01-18 Thread Donald Woods (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]

Donald Woods updated GERONIMO-1449:
---

Geronimo Info: [Patch Available]
  Fix Version: 1.1
Assign To: Donald Woods

Looks like part 1 was fixed yesterday.
Part 2 - Turns out that configs/j2ee-server/project.xml needs 
geronimo-corba_2.3_spec and geronimo-spec-corba when OpenEJB is not built with 
Geronimo.

 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: Donald Woods
 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:groupIdgeronimo-spec/dep:groupId
 dep:artifactIdgeronimo-spec-corba/dep:artifactId
 dep:version2.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



[jira] Updated: (GERONIMO-1449) Cannot build from Geronimo 1.0 src zip - issues with missing dependencies

2006-01-18 Thread Donald Woods (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1449?page=all ]

Donald Woods updated GERONIMO-1449:
---

Attachment: Geronimo-1449.patch

Attaching patch for Part 2 of the reported problem.

 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: Donald Woods
 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:groupIdgeronimo-spec/dep:groupId
 dep:artifactIdgeronimo-spec-corba/dep:artifactId
 dep:version2.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



[jira] Updated: (GERONIMO-1449) Cannot build from Geronimo 1.0 src zip - issues with missing dependencies

2006-01-11 Thread John Sisson (JIRA)
 [ 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
+

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:groupIdgeronimo-spec/dep:groupId
dep:artifactIdgeronimo-spec-corba/dep:artifactId
dep:version2.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?


  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
 +
 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:groupIdgeronimo-spec/dep:groupId
 dep:artifactIdgeronimo-spec-corba/dep:artifactId
 dep:version2.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: