jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Boston <...@tfd.co.uk>
Subject Re: Licensing of JCR in Jackrabbit
Date Tue, 05 Mar 2013 07:11:24 GMT
The jcr license is compatible with the apache license to use. The only restriction on the
jcr license is if you want to implement your own jcr implementation. If you do that you will
need to read up the conditions which iirc are available on the java specification website.

From the sound of it, you only want to use jackrabbit and build on top of it which means your
good to go.


Sent from my iPhone

On 05/03/2013, at 6:25, <sara.krishnan@oocl.com> wrote:

> Hello,
> We are evaluating Jackrabbit solution in a project that we are working on. It looks like
the JCR 1.0 or JCR 2.0 jars, which contain the JCR APIs, are not part of the non-standalone
distribution and so has to be downloaded separately. Question is if the JCR APIs found in
the separate binary, javax.jcr.* falls under the Apache license as well.  If not, how does
Jackrabbit have access to the JCR API ?
> Based on the text in the Jackrabbit project page (http://jackrabbit.apache.org/downloads.html)
> Apache Jackrabbit releases are available under the Apache License, Version 2.0<http://www.apache.org/licenses/LICENSE-2.0>.
See the NOTICE.txt file contained in each release artifact for applicable copyright attribution
notices. Some Jackrabbit components contain external code with licenses that meet Apache licensing
policies<http://www.apache.org/legal/resolved.html>. See the LICENSE.txt file contained
in each release artifact for applicable licenses.
> Here's another link that says that Apache Jackrabbit is licensed under Apache License
2.0  http://projects.apache.org/projects/jackrabbit.html
> Thanks
> Sara
> Email from OOCL is confidential and may be legally privileged.  If it is not
> intended for you, please delete it immediately unread.  The internet
> cannot guarantee that this communication is free of viruses, interception
> or interference and anyone who communicates with us by email is taken
> to accept the risks in doing so.  Without limitation, OOCL and its affiliates
> accept no liability whatsoever and howsoever arising in connection with
> the use of this email.  Under no circumstances shall this email constitute
> a binding agreement to carry or for provision of carriage services by OOCL,
> which is subject to the availability of carrier's equipment and vessels and
> the terms and conditions of OOCL's standard bill of lading which is also
> available at http://www.oocl.com.

View raw message