thanks david jencks
The contents of the m1 and m2 build openejb jars are necessarily
somewhat different, so it's desirable that they have different names:
otherwise the geronimo m2 configs build tends to pick up m1 openejb
jars. I think the easiest way to do this is to give the m2 jars m2
style groupIds. To get this started I changed the m2 openejb build
to use org.openejb. If this is the wrong groupId let me know what is
more correct and I will change it.
- openejb m2 groupId David Jencks
- Re: [openejb-dev] openejb m2 groupId David Blevins
- Re: [openejb-dev] openejb m2 groupId Jason Dillon
- Re: [openejb-dev] openejb m2 groupId David Blevins
- Re: [openejb-dev] openejb m2 groupId Jason Dillon
- Re: [openejb-dev] openejb m2 groupId Jason Dillon
- Re: [openejb-dev] openejb m2 groupId Alan D. Cabrera
