We need to make a decision on how to handle getting a non-snapshot
version of openejb for the Geronimo M1 release. In the past, we've
handled this by having a local repository in the build that copied a
revision pinned version in the local maven repository to do the build.
This type of processing is at best frowned upon by the maven release
plugin, and might even be specifically forbidden.
The openejb community is probably weeks away from having code in a state
that they would be comfortable shipping as a visible milestone, which is
a bit of a problem for getting a Geronimo M1 release out soon. If we're
going to ship something, then it really will have to be a private build
of some kind.
We already sort of have precedent with how we're handling Tomcat. At
this point, it appears the simplest approach would be to make a copy of
the openejb code in the geronimo ext tree, change the group ids to
geronimo ids and release the artifacts separately. Since this will have
different group ids, the chance of getting used as standalone openejb
components is significantly less, and this gives us a non-snapshot
version we can replace with a real release for the final version.
Thoughts on whether this doable?
Rick
