We can't take the Exolab code directly, but in the case of OpenEJB Richard and I (as well as the other current OpenEJB developers) can donate our original sources to Apache. We're all on this list and have signed and faxed in ASF contributor forms.
-David On Tue, Aug 12, 2003 at 12:06:28PM +1000, Tim Anderson wrote: > Speaking of licensing, how are sources under the Exolab license > going to be handled? Is there are requirement that all sources > have an Apache license? > > -Tim > > > -----Original Message----- > > From: David Blevins [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, 12 August 2003 5:22 AM > > To: [EMAIL PROTECTED] > > Subject: Re: junit tests -- OpenEJB > > > > > > As Dain mentions, the OpenEJB (no space) compliance test suite is > > pretty large -- took me a couple months to write. None of the > > code is OpenEJB specific and can be moved under the ASF license > > without problem. > > > > Last I heard Jacek and Tim (OpenEJB developers) were working on > > getting that moved over. > > > > -David > > > > On Mon, Aug 11, 2003 at 06:45:19PM -0500, Dain Sundstrom wrote: > > > Open EJB has a fairly massive spec test that we should be able to adopt > > > to Geronimo. I'm not sure if anyone is working on it. > > > > > > Maybe David Belvins can comment... > > > > > > -dain > > > > > > On Monday, August 11, 2003, at 06:39 PM, Erin Mulder wrote: > > > > > > > From: "Bruce Snyder" <[EMAIL PROTECTED]> > > > >> Clover will provide us with the status of which you speak. But to > > > >> break > > > >> down each requirement will certainly take a lot more work. > > It would be > > > >> very nice to try to automate this work because it is so generic. > > > >> > > > >> Sure, in the meantime, we could use the Wiki to track it manually, > > > >> but we will need to consider how the Wiki list will be converted to > > > >> the > > > >> final solution. > > > >> > > > >> I'd like to get started writing some tests tonight and get them > > > >> checked > > > >> in so let's decide what we're going to do so that efforts don't go in > > > >> the wrong direction or, even worse, get wasted. > > > > > > > > Not sure what to say yet for basic low-level unit tests, but for spec > > > > compliance tests, we could start with the following: > > > > > > > > 1. Create a page in the Wiki that lists all of the specs > > > > 2. Each spec listing links to a test coverage page > > > > 3. The test coverage page lists all of the tests, organized by > > > > chapter/section. > > > > 4. A developer notices a section with no tests and puts a note in > > > > saying > > > > he's developing one > > > > 5. Once the test is committed, that part is updated to > > refer to it > > > > by > > > > name > > > > 6. Eventually, the page lists the entire spec, with tests for each > > > > requirement > > > > > > > > A page for the EJB 2.1 spec might look something like: > > > > > > > > Chapter 7: Session Bean Components > > > > 7.8: Stateless Session Beans > > > > 7.8.2: Operations allowed in stateless session beans > > > > * test being developed by [EMAIL PROTECTED] > > > > 7.8.3: Dealing with Exceptions > > > > * > > > > org.apache.geronimo.test.ejb.TestSessionExceptionHandling > > > > > > > > Chapter 18: Exception Handling > > > > 18.3: Container Provider responsibilities > > > > 18.3.1: Exceptions from a session/entity's > > business methods > > > > * > > > > org.apache.geronimo.test.ejb.TestSessionExceptionHandling > > > > 18.3.10 Release of resources > > > > * > > > > org.apache.geronimo.test.ejb.TestExceptionResouceRelease > > > > > > > > Not too advanced, but easy to parse into a database later. Plus, it > > > > makes > > > > it simple to find areas that need tests. Of course, the more I look > > > > at > > > > this, the more it looks like an open source TCK. > > > > > > > > I can update the Wiki with the skeleton for this if you want to give > > > > it a > > > > go. It would be helpful, however, to come up with some meta tags to > > > > put in > > > > the tests themselves to make automation easier later on. > > > > > > > > Erin > > > > > > > > > > > > > > /************************* > > > * Dain Sundstrom > > > * Partner > > > * Core Developers Network > > > *************************/ > > >
