FYI, I updated maven.xml in geronimo/branches/1.0 to use svn -- this
got the Gbuild for 1.0.1-SNAPSHOT to run...
Alternative, was to remove the 'maven m:co' from the 1.0.1 build
steps. However, I don't know how to do that... We'd also need an
OpenEJB 2.0.1 gbuild to make that work... I think that's the
appropriate way forward, however...
--kevan
Begin forwarded message:
From: Kevan Miller <[EMAIL PROTECTED]>
Date: February 3, 2006 5:03:32 AM EST
To: dev@openejb.org
Subject: Re: [openejb-dev] svn conversion - done
On Feb 2, 2006, at 6:03 PM, Dain Sundstrom wrote:
On Feb 2, 2006, at 1:34 PM, David Blevins wrote:
On Feb 2, 2006, at 4:53 AM, Kevan Miller wrote:
On Feb 1, 2006, at 11:28 PM, David Blevins wrote:
Alright, svn conversion is done.
svn co svn+ssh://openejb.org/home/projects/openejb/scm/trunk/
openejb2
http://svn.openejb.codehaus.org
David,
This broke OpenEJB's Gbuild. It also broke Geronimo's build
process.
Fixed now.
Important to note that G 1.0 buildnotes are no longer valid. I
think we should be moving to a published build model for
OpenEJB, to avoid this problem in the future. Agreed?
You are preaching to the choir. David J. and Dain, what are
your current thoughts on this?
I don't think it is possible yet. There interface between openejb
and geronimo is HUGE. When ever you want to change something in
openejb you normally need to change stuff in geronimo, so you need
to build everything together. This is super easy with maven2 but
until we are on maven2 I say we stick with what we've got.
Agreed that this is an issue for the combined OpenEJB/Geronimo
developer.
Not quite so much for the Geronimo-only developer. However, he/she
would suffer a build break when he/she picks up a Geronimo update
and is either performing an offline build or a new OpenEJB hasn't
been published.
And little, if at all for a Geronimo built-from-source user.
For now, I'd recommend removing openejb from the m:co goal in the
branches/1.0 stream and updating build related documentation.
Thoughts?
--kevan