On 2017-12-05 11:35, Marcel Reutegger wrote:
Hi,
On 05/12/17 09:51, Julian Reschke wrote:
This seems to originate from
<https://issues.apache.org/jira/browse/JCR-3598> - "Oak in
Jackrabbit deployment packages" - which is still open today.
Can we either remove this, or clarify what Oak version should be
used here?
I would rather not remove this, but update to the most recent stable
version.
Per branch, or globally? So would Jackrabbit 2.12 use Oak 1.6.*, or
something from the "matching" Oak branch?
I don't think we can do this globally. If these components are in use,
even though I doubt it, user may be forced to upgrade the repository
between patch releases. I would keep the branches on the 1.0.x releases
and update the dependency to the most recent stable 1.0.x. For trunk, I
would update to the most recent 1.6.x.
OK. FWIW, I just tried an upgrade to 1.6 and it fails due to changes in
the oak-upgrade API (which is in use for some IT tests).
I'm still in favor of this replacement, but it probably means
Jackrabbit components that bundle other components would have to go
on their own release schedule.
Understood, but that's additional work, too.
FWIW, we already do have oak-standalone etc, right? Why duplicate this?
Good question. The more I think about those components, the more I
consider them samples and not components the Jackrabbit project should
deliver/release as binaries.
I don't think you would ever deploy jackrabbit-webapp as is. In my view,
this is a sample and should be released with sources only (if at all).
The same applies to jackrabbit-standalone, which bundles the
jackrabbit-webapp.
+1
Btw, there is no oak-standalone. Do you mean oak-run? This one is
different because it contains various tools that can indeed be used as is.
oak-examples/standalone
Best regards, Julian
