Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=H8f26i0jtYig6I9RqTy4YkwSybPLE9JHP1qXfq+KwJmyJdLtOlrm5WKdFOBtS35N;
  h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <46FBFC58.6020407@earthlink.net>
Date: Thu, 27 Sep 2007 14:54:16 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: 2.0.2 Build failing
References: <46FBB134.3070009@earthlink.net>
In-Reply-To: <46FBB134.3070009@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Joe Bohn wrote:
> It looks like we're in an incompatible state at the moment between 
> Geronimo-2.0 and Openejb trunk.  Some changes went in yesterday to 
> openejb (http://svn.apache.org/viewvc?rev=579817&view=rev) that altered 
> org.apache.openejb.spi.SecurityService and require comparable changes in 
> Geronimo.  Does anybody know the status of the Geronimo changes?


I'm going to switch the Geronimo-2.0 dependency on openejb from 
3.0.0-SNAPSHOT (trunk) to 3.0-beta-1.  This should hopefully get around 
this build problem since the SecurityService change didn't go into 
3.0-beta-1 and get geronimo 2.0.2 on a stable openejb release as we get 
closed to getting it out the door.

Joe