On Feb 6, 2007, at 5:06 AM, anita kulshreshtha wrote:
--- Jacek Laskowski <[EMAIL PROTECTED]> wrote:
On 2/6/07, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
This will introduce cyclic dependency between openejb and geronimo
build. David B. had an alternate solution.
Does it mean that M2 is not able to handle cyclic dependency in a
satisfactory manner?
I have not tried this to give a definite answer.. The only
situation where one would see the effects of this are during an
offline
build of geronimo and openejb from a clean repo. One must build
geronimo until the build fails for openejb, then build openejb and
then
continue with rest of the geronimo build.
The really big issue is at release time, it's an absolute nightmare.
The worst.
This is a problem that has frustrated everyone and is one of the
things we really focused on and fixed in OpenEJB 3 and the new
integration (hallelujah!). Here's an email from the not to distant
past.
http://mail-archives.apache.org/mod_mbox/geronimo-dev/200612.mbox/%
[EMAIL PROTECTED]
-David
I saw the comment of Dave B. where he had said that there should've
been more exclude's in OpenEJB's poms. When I compiled OE3 yesterday,
I noticed lots of libs of Geronimo from past releases and thought to
get rid of them, but didn't have time. I'm investigating it now.
Compiling openejb with 1.2-beta is working satisfactorily. the
configs and hence assembled servers do not use any 1.2-beta jars. We
can continue to do the same as long as it compiles with 1.2-beta. The
exclusions do _confuse_ maven about which version of openejb specs to
use. The results are different from top, 'modules' and
'geronimo-openejb-builder' directory! Now geronimo and openejb use
same
version of openejb spec hence this problem is not there.
Thanks
Anita
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
______________________________________________________________________
______________
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html
