On 10/28/06, David Blevins <[EMAIL PROTECTED]> wrote:
Ok, I took look through where you're going and here's a slightly
altered proposal.
We group the tests with the beans as such:
openejb-footests/src/main/ # this is where the beans will go
openejb-footests/src/test/ # this is where the client test code
will go
We setup the poms to package and publish the test code with the beans:
http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html
That will avoid spreading the code for a single test between two
modules and avoids the "bucket" module that would contain all test
client code for all modules and would needlessly have a dependency on
all modules.
That sound very promising. I like it.
Couple thoughts on the poms:
- the parent would lineage would be org.apache.openejb:itests ->
org.apache.openejb:openejb
- the groupId would be org.apache.openejb
Unless I'm mistaken, it implies that itests are a submodule of the
top-level module of OpenEJB, doesn't it? If so, I'm fine with it, too.
You and put any geronimo-specific plugins, descriptors, or
dependencies in pom.xmls (modules) in geronimo svn using any layout
you choose. Those modules would just declare dependencies on the
openejb test libraries they wish to reuse.
Does it mean that Geronimo tests would be dependent on OpenEJB? These
should be separate as much as possible. If there's no other way, let's
start with it and think about it later.
That should be fine
unless you also plan to redo all the test source code to something
other than junit or introduce code dependencies on geronimo-specific
bits of test framework.
That's what I didn't catch. What do you mean by that?
Jacek
--
Jacek Laskowski
http://www.jaceklaskowski.pl
