On Apr 3, 2008, at 9:02 AM, Joe Bohn wrote:
Donald Woods wrote:
Also, it seems that we need an updated tranql-connector-db2-xa-1.2
build, to fix a known problem with the trace file setting.
See http://www.nabble.com/forum/ViewPost.jtp?
post=16404097&framed=y&skin=134
Thanks Donald.
I asked on that thread if updating to the newer connector actually
resolved the issue.
Does anybody happen to know if there is a release planned in the
near future for this connector should it prove to be the solution
for this issue? If not, how hard would it be to add create one (I
guess that's a question for you David)? Also, I'm not sure how
these connectors are typically released ... would we upgrade all of
the connectors or just the db2-xa connector?
Just that one. I'll try for today or tomorrow. IIRC we haven't been
having votes on tranql stuff so I think I just need to review the
build state and release it.
thanks
david jencks
Perhaps it would suffice to just include documentation on how to
upgrade the connector to resolve the issue and deliver the released
connector in 2.1.2 and/or 2.2.
Joe
-Donald
Joe Bohn wrote:
I think it's about time we got a 2.1.1 release out. The main
motivation is to deliver a fix for the PortletSecurityException
when using https on the admin console (https://issues.apache.org/
jira/browse/GERONIMO-3855). but there are a lot of other fixes
that have been integrated as well.
The TCK looked good with a recent run ... so I think that should
not be an issue.
As far as snapshots go, it looks like we're now pulling in a
snapshot for javamail that we would need to resolve (geronimo-
javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
Are there any other changes/fixes that we should be looking to
include prior to a release?
I am willing to get my feet wet as the release manager unless
somebody else wants to pick it up.
Joe
