We have done some test here with the tranql SQLServer 2000 and 2005 XA
connector (https://issues.apache.org/jira/browse/GERONIMO-4279), and TranQL
Informix XA connector (https://issues.apache.org/jira/browse/GERONIMO-4365),
both look good. So they should be ready to get into Geronimo 2.1.4.
Still
Jay,
Updating OpenEJB 3.0.1 to xbean 3.5 will require 2.0.3 and 2.1.4 to
update the asm 3.1 library (and that will need even more changes). I
know some other libs have deps on the asm lib so we might run into
problems later on.
How about we only upgrade xbean-naming to 3.5 first and leave other
x
Jarek,
I got spoiled by having the integration tests automatically run on 2.2.
I had hoped that the tests were broken before I started - but
unfortunately, it really was me that broke them.
I will find and fix the problem.
Thanks for alerting me to it.
Jay
Jarek Gawor wrote:
> Jay,
>
> Pleas
Jay,
Please run all tests including the integration tests before
committing. Looks like deployment of some apps is failing after the
recent changes, for example see:
http://people.apache.org/builds/geronimo/server/binaries/2.0/20090204/logs-0200-tomcat/test.log
Jarek
On Wed, Feb 4, 2009 at 9:55
All of the 2.0.3 build issues are fixed.
I will try building 2.0.3 with XBeans 3.5 now and let you all know what
happens.
If it will build, then I might take a look to see whether I can figure
out what changes are necessary for OpenEJB 3.0.1 to use XBeans 3.5 too.
Jay
Jay D. McHugh wrote:
> The
+1
Thanks
Manu
On Wed, Feb 4, 2009 at 1:13 AM, Jarek Gawor wrote:
> Hi,
>
> I think it's time for Geronimo 2.1.4 release. We've had a lot of
> important fixes since 2.1.3 and we should get them out to our users.
> And if we agree, I would also like to volunteer to be a release
> manager for this
Thanks Jarek!
The JIRA list in the status page looks like pretty old (dated as "20081119 @
10:15 EST"). I can make it updated if this helps...
BTW, would someone please help to review and commit the fix for
GERONIMO-4525? One user wants to call the shell commands and check the exit
code according
Those classes that Geronimo is looking for are OpenEJB classes.
Jay
Jay D. McHugh wrote:
> The problem is with the version of ASM that is brought in when using a
> higher version of XBeans.
>
> OpenEJB is using a method that has been removed:
> org.objectweb.asm.ClassReader.accept
>
> And Geron
The problem is with the version of ASM that is brought in when using a
higher version of XBeans.
OpenEJB is using a method that has been removed:
org.objectweb.asm.ClassReader.accept
And Geronimo (already - not counting XBeans 3.5) is using classes that
have been removed:
LinkResolver
UniqueDefau
Thanks for the info Jay and for doing some more digging.
I don't really have a strong desire to push everything to xBean 3.5. I
was just trying to eliminate the use of multiple xBean versions as this
could potentially cause problems (and confusion) for our users.
It looks like we originally
Hey everyone,
If we want to get OpenEJB 3.0.1 to move up to XBeans 3.5, then I think
that we'll need to chip in to resolve the problems that pop up when you
use a version greater than 3.4.1.
That was the highest version (available at the time) that could be used
in the OpenEJB 3.0 branch without
I was relaying the information second-hand ... so it's very possible I
got it wrong.
It looks like there is a dependency xBean in OpenEJB ... but it's 3.4.1
rather than 3.3 (as we have in the branches/2.1). So, perhaps if we can
convince OpenEJB 3.0.x to xBean 3.5 we can then make the referen
I don't see any dependencies on Xbean in OpenJPA 1.0.x or 1.2.x. Maybe
you're thinking about OpenEJB?
-Donald
Joe Bohn wrote:
I agree we should get a 2.1.4 release out ... and you certainly have my
vote for release manager!
The only thing I would add to the list is to get our xBean refere
Agree and thanks for volunteering.
-Donald
Jarek Gawor wrote:
Hi,
I think it's time for Geronimo 2.1.4 release. We've had a lot of
important fixes since 2.1.3 and we should get them out to our users.
And if we agree, I would also like to volunteer to be a release
manager for this release.
Lo
+1 Thanks for volunteering to be the release manager!
Lin
On Tue, Feb 3, 2009 at 2:43 PM, Jarek Gawor wrote:
> Hi,
>
> I think it's time for Geronimo 2.1.4 release. We've had a lot of
> important fixes since 2.1.3 and we should get them out to our users.
> And if we agree, I would also like to v
I agree we should get a 2.1.4 release out ... and you certainly have my
vote for release manager!
The only thing I would add to the list is to get our xBean references to
a consistent versions. I noticed this as I was updating branches/2.1
and trunk to pull in the newly released xBean 3.5. I
16 matches
Mail list logo
