The Apache Jenkins build system has built Jackrabbit Oak (build #1268)
Status: Failure
Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/1268/ to
view the results.
Changes:
[catholicon] OAK-7284: Reindexing using --doc-traversal-mode can hit
On Tue, 2018-02-27 at 12:21 -0500, Matt Ryan wrote:
> Are there use cases where users should prefer Jackrabbit over Oak?
> Or is
> Oak considered a full replacement for Jackrabbit in every case?
My understanding is that Jackrabbit is a reference implementation of
the spec, with all bells and
The Apache Jenkins build system has built Jackrabbit Oak (build #1266)
Status: Failure
Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/1266/ to
view the results.
Changes:
[reschke] OAK-7292: RDB*Store: update tomcat jdbc dependency to 8.5.28
[mreutegg] OAK-7291:
Yes, I prefer to keep that Committer = PMC to the extent that it is possible,
so please remove my commit bit as well.
We have a longstanding tradition for HTTP Server that any of the emeritus folks
are welcome to come back at any time in the future. I expect that will be the
case for
Interesting.
Are there use cases where users should prefer Jackrabbit over Oak? Or is
Oak considered a full replacement for Jackrabbit in every case?
-MR
On February 27, 2018 at 8:53:53 AM, Robert Munteanu (romb...@apache.org)
wrote:
Hi,
Recent questions to the jackrabbit user's list lead
Hi,
Recent questions to the jackrabbit user's list lead me to believe that
users are still picking Jackrabbit 2.x as a first implementation
choice. I believe that we should be pointing them to Oak instead, as
that's (IMO) the better documented, supported and implemented version
of a JCR
Hi,
JDK 11 builds are our, in case someone wants to do some early testing.
http://jdk.java.net/11/
Robert
Konrad Windszus created JCRVLT-279:
--
Summary: Emit warning/error in case embedded file/subpackage is
overwritten by jcrRootSourceDirectory
Key: JCRVLT-279
URL: https://issues.apache.org/jira/browse/JCRVLT-279
https://issues.apache.org/jira/browse/OAK-7289
(potential NPE in well-intended exception handler)
Hi Roy,
Let me thank you for all the hard work you put into Jackrabbit and its
related projects! While it is sad to see long time members go, I'm sure
we are still going to see you around with all your involvement in the
ASF. I certainly hope to continue receiving guidance from your side if
10 matches
Mail list logo