Hi, > g) Or as a last resort, abandon the idea of a joint deployment > package. Jackrabbit Classic and Oak would be shipped in separate > deployment artifacts.
this is my preferred option. this would also send out the message that Oak is meant to replace Jackrabbit 2.x. I'd keep the Jackrabbit 2.x line for maintenance purpose and either release 2.8.x bugfix releases in the future or if needed a 2.10 and so on... For Oak I'd either release it as Oak 1.0 or Jackrabbit 3.0. But neither would contain any legacy code from Jackrabbit 2.x, except maybe for migration purposes. Regards Marcel
