On 2017-12-05 12:45, Marcel Reutegger wrote:
Hi,
On 05/12/17 11:47, Julian Reschke wrote:
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
Oh, right. I was only looking at the top level modules. Thanks for the
pointer. So, it looks like in Oak standalone and webapp are already
considered examples.
I guess this is yet another reason for moving also the Jackrabbit
equivalents to examples and not release them anymore.
But that doesn't answer your question why those modules are duplicated
and what we should do with the dependencies from Jackrabbit to Oak.
I see two options:
- Keep the duplicate modules, but remove the Oak dependency in Jackrabbit
That would be my preference, for simplicity. Of course then the next
question would be: just in trunk, or everywhere?
- Remove the modules in Jackrabbit and change the Oak variants to also
work with Jackrabbit
Best regards, Julian
