You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by fi...@apache.org on 2006/03/25 20:42:23 UTC

svn commit: r388801 - in /jackrabbit/branches/1.0: jackrabbit/src/site/xdoc/about.xml jcr-rmi/README.txt jcr-rmi/project.xml

Author: fielding
Date: Sat Mar 25 11:42:22 2006
New Revision: 388801

URL: http://svn.apache.org/viewcvs?rev=388801&view=rev
Log:
JCR-373: remove or fix references to incubator

Modified:
    jackrabbit/branches/1.0/jackrabbit/src/site/xdoc/about.xml
    jackrabbit/branches/1.0/jcr-rmi/README.txt
    jackrabbit/branches/1.0/jcr-rmi/project.xml

Modified: jackrabbit/branches/1.0/jackrabbit/src/site/xdoc/about.xml
URL: http://svn.apache.org/viewcvs/jackrabbit/branches/1.0/jackrabbit/src/site/xdoc/about.xml?rev=388801&r1=388800&r2=388801&view=diff
==============================================================================
--- jackrabbit/branches/1.0/jackrabbit/src/site/xdoc/about.xml (original)
+++ jackrabbit/branches/1.0/jackrabbit/src/site/xdoc/about.xml Sat Mar 25 11:42:22 2006
@@ -22,38 +22,26 @@
         <section name="Apache Jackrabbit">
 <p>
 <!-- <a href="http://www.apachecon.com/2005/US/index.html" class="externalLink" title="External Link"><img src="http://www.apache.org/images/ac2005us_white_184x80.jpg"  width="184" height="80" border="0" title="ApacheCon US 2005" align="right" valign="top" alt="ApacheCon 2005 US"/></a> -->
-The Apache Jackrabbit Project was formed to develop an open source
-implementation of the Content Repository for Java Technology API (JCR),
+The Apache Jackrabbit Project is responsible for creating open source
+software related to the Content Repository for Java Technology API (JCR),
 as specified through the Java Community Process in
-<a href="http://www.jcp.org/en/jsr/detail?id=170">Java Specification Request 170 (JSR 170)</a> and
-<a href="http://www.jcp.org/en/jsr/detail?id=170">JSR 283</a>.
-<a href="http://www.day.com/">Day Software</a>, the JCR specification lead,
-has licensed an initial implementation of the JCR reference implementation for
-use as seed code for this project. JCR specifies an API for application
-developers (and application frameworks) to use for interaction with modern
-content repositories that provide content services such as searching,
-versioning, transactions, etc.
+<a href="http://www.jcp.org/en/jsr/detail?id=170">JSR 170</a> and
+<a href="http://www.jcp.org/en/jsr/detail?id=283">JSR 283</a>.
+JCR specifies an API for application developers (and application frameworks)
+to use for interaction with modern content repositories that provide content
+services such as searching, versioning, transactions, etc.
 </p>
 <p>
-Jackrabbit's implementation began as a proposal within the
-<a href="http://jakarta.apache.org/slide/index.html">Jakarta Slide</a>
-project, but has since attracted interest from multiple projects with the
-<a href="http://www.apache.org/">Apache Software Foundation</a>, including
-Slide, Cocoon, Lenya, XML Indexing, Axion, and Derby. We are also looking at
-integration with projects such as Beehive, Maven, and Portals.
+<a href="http://www.day.com/">Day Software</a>, the JCR specification lead,
+licensed to the Apache Software Foundation the initial source code of the
+JCR reference implementation for use as seed code for this project.
+Development of the RI and TCK continues within this project, with participation
+from the entire community in improving the implementation and refining the
+test cases.
 </p>
 <p>
-The purpose of this incubation period is to attract additional contributors
-from other Apache projects and from the various expert group companies,
-learn the Apache way of doing things, and allow the developers to focus on this
-interface/implementation rather than all of the existing projects that might
-want to use it. We hope to improve collaboration on the code base by moving
-all of the active developers and authors to Apache, bring in as many of the
-Apache veterans as wish to get involved, and open it up to all of the 22 expert
-group companies. Development of the JCR RI and TCK will occur in this project
--- Day Software plans to continue participation in Jackrabbit and use the code
-in the official (binary) RI and TCK releases, allowing developers to beta test
-against the open source versions as well as the official versions.
+Our project is open to new contributors. To get involved, please subscribe
+to the mailing lists and dive in.
 </p>
         </section>
     </body>

Modified: jackrabbit/branches/1.0/jcr-rmi/README.txt
URL: http://svn.apache.org/viewcvs/jackrabbit/branches/1.0/jcr-rmi/README.txt?rev=388801&r1=388800&r2=388801&view=diff
==============================================================================
--- jackrabbit/branches/1.0/jcr-rmi/README.txt (original)
+++ jackrabbit/branches/1.0/jcr-rmi/README.txt Sat Mar 25 11:42:22 2006
@@ -5,7 +5,7 @@
 JCR-RMI is a transparent Remote Method Invocation (RMI) layer for
 the Content Repository for Java Technology API (JCR). The layer makes
 it possible to remotely access JCR content repositories. JCR-RMI is
-developed as a part of the incubating Apache Jackrabbit project, but
+developed as a part of the Apache Jackrabbit project, but
 the implementation is compatible with all JCR content repositories.
 
 License (see also LICENSE.txt)

Modified: jackrabbit/branches/1.0/jcr-rmi/project.xml
URL: http://svn.apache.org/viewcvs/jackrabbit/branches/1.0/jcr-rmi/project.xml?rev=388801&r1=388800&r2=388801&view=diff
==============================================================================
--- jackrabbit/branches/1.0/jcr-rmi/project.xml (original)
+++ jackrabbit/branches/1.0/jcr-rmi/project.xml Sat Mar 25 11:42:22 2006
@@ -28,7 +28,7 @@
     JCR-RMI is a transparent Remote Method Invocation (RMI) layer for
     the Content Repository for Java Technology API (JCR). The layer makes
     it possible to remotely access JCR content repositories. JCR-RMI is
-    developed as a part of the incubating Apache Jackrabbit project, but
+    developed as a part of the Apache Jackrabbit project, but
     the implementation is compatible with all JCR content repositories.
   </description>
   <shortDescription>Transparent RMI layer for the JCR API</shortDescription>