Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer;
  b=ZnQhxMPA8sNC05g5pGvitsw3e4xp4TP+t50prtMfnXXgw7NGDF9/y+fTI7A057A4gD7WIPHQcUG3zcaXSarshu0GgrDvaOocRQtrNZ4lnikXRI98qy4UDpjwezmFgJC+nqwIRxuXAJI2fK49l9/E9z9g6VqGarS6qMrDxGHJlE0=
  ;
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: components dependencies
From: David Jencks <david_jencks@yahoo.com>
In-Reply-To: <4BB9E05B.9040403@gmail.com>
Date: Mon, 5 Apr 2010 11:20:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C7EB954-9A90-4820-9A40-1E1E85651F05@yahoo.com>
References: <4BB9E05B.9040403@gmail.com>
To: dev@geronimo.apache.org


On Apr 5, 2010, at 6:06 AM, Rick McGuire wrote:

> This is sort of related to the earlier email I sent out about the =
snapshot dependencies.  In looking at the dependencies of the =
subprojects in the geronimo components tree, I find what appear to be a =
few problems we should probably correct:
>=20
> geronimo-schema-javaee_6:  This is ok as it stands, but should we move =
the latest verions of the java 1.4 and java 5 schemas into the =
components tree rather than leaving them in the restricted TCK tree?
>=20
> geronimo-jaspi:  This is building with the 2.1 version of the jaxb =
specs and the older release of the stax api spec.  It also has =
dependencies on non-bundle versions of sxc-jaxb, woodstox, and the =
jaxb-impl.  The jaxb-impl is also at the 2.1.7 level rather than the 2.2 =
level used by the server.  This is a fairly simple update, but would =
have dependencies on geronimo bundles components, which really suggests =
those should be moved out of the server tree as separately buildable =
components.  I suspect it would make the bootstrapping process easier if =
they could be handled that way.  On the downside, this creates another =
level of release artifacts that require voting and a release process.
>=20
>  geronimo-jaspi-openid:  Building with the older version of the jaspic =
spec jar and servlet 2.5 spec.  Should this be using the java ee 6 api =
versions?  This is also using the 1.0-SNAPSHOT version of the =
geronimo-jaspic build, rather than the current 1.1-SNAPSHOT version.

I'm not sure we want to push the jaspi support into java 6 and the =
latest apis as it might inhibit people using it with java 5 projects.  I =
don't feel too strongly about it though.

david jencks
>=20
> geronimo-connector/geronimo-transaction:  The connector 1.6 spec =
version is the 1.0-EA-SNAPSHOT.  This should be updated to the latest =
spec snapshot.
>=20
> Thoughts on updating this?  The issue of the use of the geronimo =
bundles probably needs to be resolved ASAP so we can get release votes =
out for those components in the very near future.
>=20
> Rick