Yes, that is where it dies for me too.
Looks like you need to build openejb2 by hand to get around this.
This is soooo annoying! I really think that we should use a
svn:external to pull in the openejb2 source so that a simple `mvn
install` at the G root will have a greater chance of actually working
each time.
It is a huge PITA to get halfway through a build to find out that
openejb artifacts are out of sync.
I just want to svn co, mvn install and have it work! I think that is
what most folks who build the source want to.
--jason
On Nov 21, 2006, at 3:21 PM, toby cabot wrote:
On Tue, Nov 21, 2006 at 02:32:26PM -0800, Jason Dillon wrote:
Can you try to build again, w/o -Dstage=bootstrap. configs might
fail, but that is another problem...
But if you don't see missing deps on plugins, then this doc change
should be reverted.
I blew away ~/.m2/repository/org/apache and did a build and it
downloads a bunch of stuff and definitely gets past where it used to
fail, so I guess the bootstrap is no longer needed. It fails in
configs/openejb-corba-deployer but I guess that's a different problem.
Thanks,
Toby
