Am 31.01.2012 22:07, schrieb Tom Ware:
The reason we are considering Orbit is that the code we are spinning off is in a
javax package (javax.persistence). It is a third party library - in that it is
a library we depend on to run that is potentially used by other parties that do
not use our project's code. The unusual part about it is that we are both the
main contributers to the Eclipse project that uses it and the "3rd party" the
provides the library.
javax.persistence is in Orbit already. We need to make sure that there
aren't multiple different versions of it flying around. Thus, I think
it's great to have the EclipseLink project contributing their version of
javax.persistence to Orbit and ensuring that it will be maintained going
forward. A big +1 from my side.
Tom, are there any modifications you did to javax.persistence that
aren't implemented in the "official" javax.persistence package?
Usually Orbit contains binary bundles. Thus, I wonder if the source has
a better home in a Git repository owned by the EclipseLink project
itself. Just the binary bits would be published to Orbit.
David, I think the only other option we have is removing (deprecating?)
3rdparty packages from Orbit and telling people to use the version
maintained by XYZ at ABC. That does sound confusing, though.
orbit-dev mailing list