You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by ju...@apache.org on 2012/01/10 19:51:06 UTC
svn commit: r1229679 [12/12] - /jackrabbit/site/trunk/content/
Added: jackrabbit/site/trunk/content/shared-j2ee-resource-howto.mdtext
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/shared-j2ee-resource-howto.mdtext?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/shared-j2ee-resource-howto.mdtext (added)
+++ jackrabbit/site/trunk/content/shared-j2ee-resource-howto.mdtext Tue Jan 10 18:50:59 2012
@@ -0,0 +1,85 @@
+Title: Shared J2EE Resource HOWTO
+This document describes how to use a Jackrabbit content repository in the
+deployment model 2: Shared J2EE Resource. In this deployment model, a
+central content repository resource managed by an application server is
+used by multiple different applications. See the [JCR client application HOWTO](jcr-client-application-howto.html)
+ for instructions on how to use the configured content repository.
+
+This how-to contains instructions for Tomcat versions 4.x and 5.x. It
+should be easy to modify the instructions for other container environments.
+
+<a name="SharedJ2EEResourceHOWTO-Tomcatinstructions"></a>
+## Tomcat instructions
+
+Follow the steps below to setup a model 2 Jackrabbit deployment for your
+Tomcat 4.x or 5.x installation. Example code for both versions of Tomcat is
+included after this overview.
+
+1. Place the Jackrabbit jar file and all the dependencies (including the JCR
+API jar file) under _Tomcat folder_/common/lib.
+1. Register the bindable repository factory as a global resource.
+1. Link the global resource to a context scoped JNDI address.
+
+<a name="SharedJ2EEResourceHOWTO-Step2-Resourceconfiguration"></a>
+### Step 2 - Resource configuration
+
+Note: This step is essentially the same as step 2 in the Model 1 HOWTO. The
+only differences are in the (arbitrary) naming of the resource and placing
+of the configuration elements. The difference in the end result is that the
+configured repository is bound to the global JNDI context instead of a
+local one. In Tomcat 4.x and 5.0, add the following snippet in server.xml
+under the GlobalNamingResources element.
+
+
+ <Resource name="jcr/globalRepository"
+ auth="Container"
+ type="javax.jcr.Repository"/>
+
+ <ResourceParams name="jcr/globalRepository">
+ <parameter>
+ <name>factory</name>
+
+<value>org.apache.jackrabbit.core.jndi.BindableRepositoryFactory</value>
+ </parameter>
+ <parameter>
+ <name>configFilePath</name>
+ <value>[full path to repository.xml]
+</value>
+ </parameter>
+ <parameter>
+ <name>repHomeDir</name>
+ <value>[full path to the repository home folder]
+</value>
+ </parameter>
+ </ResourceParams>
+
+
+In Tomcat 5.5, add the following snippet in server.xml under the
+GlobalNamingResources element.
+
+
+ <Resource name="jcr/globalRepository"
+ auth="Container"
+ type="javax.jcr.Repository"
+
+factory="org.apache.jackrabbit.core.jndi.BindableRepositoryFactory"
+ configFilePath="[full path to repository.xml"
+ repHomeDir="[full path to the repository home folder]
+"/>
+
+
+<a name="SharedJ2EEResourceHOWTO-Step3-Resourcelink"></a>
+### Step 3 - Resource link
+
+In Tomcat versions 4.x and 5.0, add the following snippet in server.xml
+under the Context element of your web application. In Tomcat version 5.5,
+add the snippet in your application's context.xml or
+$CATALINA_HOME/conf/_enginename_/_hostname_/_webappname_.xml. If you prefer
+central configuration, you can add the configuration to
+$CATALINA_HOME/conf/context.xml.
+
+
+ <ResourceLink name="jcr/repository"
+ global="jcr/globalRepository"
+ type="javax.jcr.Repository"/>
+
Propchange: jackrabbit/site/trunk/content/shared-j2ee-resource-howto.mdtext
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/source-repository.cwiki
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/source-repository.cwiki?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/source-repository.cwiki (added)
+++ jackrabbit/site/trunk/content/source-repository.cwiki Tue Jan 10 18:50:59 2012
@@ -0,0 +1,3 @@
+Apache Jackrabbit uses [Subversion|http://subversion.tigris.org/] to manage source code. See the [Subversion book|http://svnbook.red-bean.com/] and the Apache [instructions|http://www.apache.org/dev/version-control.html] for using Subversion.
+
+The Jackrabbit source code is available at http://svn.apache.org/repos/asf/jackrabbit/ and can also be browsed using the [ViewVC|http://viewvc.tigris.org/] interface at http://svn.apache.org/viewvc/jackrabbit/.
Propchange: jackrabbit/site/trunk/content/source-repository.cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/source-repository.mdtext
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/source-repository.mdtext?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/source-repository.mdtext (added)
+++ jackrabbit/site/trunk/content/source-repository.mdtext Tue Jan 10 18:50:59 2012
@@ -0,0 +1,10 @@
+Title: Source Repository
+Apache Jackrabbit uses [Subversion](http://subversion.tigris.org/)
+ to manage source code. See the [Subversion book|http://svnbook.red-bean.com/]
+ and the Apache [instructions|http://www.apache.org/dev/version-control.html]
+ for using Subversion.
+
+The Jackrabbit source code is available at
+http://svn.apache.org/repos/asf/jackrabbit/ and can also be browsed using
+the [ViewVC](http://viewvc.tigris.org/)
+ interface at http://svn.apache.org/viewvc/jackrabbit/.
Propchange: jackrabbit/site/trunk/content/source-repository.mdtext
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/standalone-server.cwiki
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/standalone-server.cwiki?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/standalone-server.cwiki (added)
+++ jackrabbit/site/trunk/content/standalone-server.cwiki Tue Jan 10 18:50:59 2012
@@ -0,0 +1,112 @@
+Each Jackrabbit release comes with a pre-built and runnable standalone server jar. It's the easiest way to get started with Jackrabbit, simply [download|Downloads] and start the jar to get a fully functional JCR content repository. The rest of this page documents what else you can do with the standalone server.
+
+{toc:minLevel=2}
+
+h2. Running the standalone server
+
+You need Java version 5 or higher to run the Jackrabbit standalone server. To start the server, double-click on the standalone jar file, or invoke it on the command line.
+
+{code:none}
+$ java -jar jackrabbit-standalone-1.6.0.jar
+Welcome to Apache Jackrabbit!
+-------------------------------
+Using repository directory jackrabbit
+Writing log messages to jackrabbit/log
+Starting the server...
+Apache Jackrabbit is now running at http://localhost:8080/
+^C
+Shutting down the server...
+-------------------------------
+Goodbye from Apache Jackrabbit!
+{code}
+
+After staring the server, you can point your browser to [http://localhost:8080/] to see Jackrabbit in action. Use the {{--port}} command line option to specify an alternative if the default port 8080 is already used by another program.
+This is what the server should look like in your browser:
+
+!standalone500.png|align=center!
+
+By default the server will look for a content repository in the {{./jackrabbit}} directory and a repository configuration file in a {{repository.xml}} file within the repository directory. The repository directory is automatically created if it does not already exist, and a configuration file with the default configuration is created if no configuration is found.
+
+Server, access, and repository log messages are written to log files in the {{log}} subdirectory within the repository directory.
+
+You can stop the server by pressing {{Ctrl-C}} or by sending it a standard termination signal. The server will then close the content repository and exit cleanly.
+
+h2. Command line options
+
+You can customize the operation of the standalone server with the following command line options (with defaults in parenthesis).
+
+{code:none}
+$ java -jar jackrabbit-standalone-1.6.0.jar --help
+usage: java -jar jackrabbit-standalone-1.6.0.jar [-?] [-b] [-c <arg>] [-C
+ <arg>] [-d] [-f <arg>] [-h <arg>] [-l] [-n] [-p <arg>] [-q] [-r <arg>] [-R
+ <arg>]
+ -?,--help print this message
+ -b,--backup create a backup of the repository
+ -c,--conf <arg> repository configuration file
+ -C,--backup-conf <arg> backup repository configuration file
+ -d,--debug enable debug logging
+ -f,--file <arg> location of this jar file
+ -h,--host <arg> IP address of the HTTP server
+ -l,--license print license information
+ -n,--notice print copyright notices
+ -p,--port <arg> TCP port of the HTTP server (8080)
+ -q,--quiet disable console output
+ -r,--repo <arg> repository directory (jackrabbit)
+ -R,--backup-repo <arg> backup repository directory (jackrabbit-backupN)
+{code}
+
+You may want to increase the maximum amount of heap memory available to the Java virtual machine especially if you plan to have lots of concurrent clients accessing the repository or want to perform large batch operations.
+
+{code:none}
+$ java -Xmx256m -jar jackrabbit-standalone-1.6.0.jar
+{code}
+
+h2. Web interface
+
+The web interface you see at [http://localhost:8080/] is a simple web application built on top of the content repository. It contains some basic instructions on how to access the repository and comes with the following utility tools:
+
+* Populate ([http://localhost:8080/populate.jsp])
+ This tool populates the default workspace with example documents found on the web based on a Google search. This is an easy way to get some semi-random test content into the repository.
+* Search ([http://localhost:8080/search.jsp])
+ This tool uses the full text search feature to find content within the default workspace of the repository. To see the search feature in action, first add some content to the repository with the Populate tool and then try to search for the documents with the Search tool.
+* Browse ([http://localhost:8080/repository/default/])
+ The built-in WebDAV feature allows you to browse the file ({{nt:file}}) and folder ({{nt:folder}}) nodes within the repository. See the WebDAV section below for all the other things you can do with this tool! Note that the server will by default accept any username and password combination.
+
+h2. WebDAV access
+
+The simple repository browser you can see at [http://localhost:8080/repository/default/] is actually a fully featured WebDAV server backed by the content repository. You can mount this address as a WebDAV share to your normal filesystem and treat it as you would any shared network folder. This feature is especially useful for copying large amounts of files or folders to or from the repository. Note that this feature is limited to standard files and folders, any more fine-grained JCR content will simply not be visible.
+
+The repository also exposes an alternative WebDAV access point at [http://localhost:8080/server/] for more fine-grained content access. This access point implements a number of advanced WebDAV features that are not normally seen in plain file-based WebDAV servers. You will need a feature-rich WebDAV or HTTP client to access the full power of this interface. With the Jackrabbit spi2dav component you can even get full remote JCR access over the WebDAV features and some custom extensions available through this access point.
+
+h2. RMI access
+
+In addition to the WebDAV access points, the standalone server also supports remote JCR access over RMI. After adding the JCR API and the jackrabbit-jcr-rmi jars to your classpath, you can access the repository remotely with the following code:
+
+{code}
+import org.apache.jackrabbit.rmi.repository.URLRemoteRepository;
+
+Repository repository =
+ new URLRemoteRepository("http://localhost:8080/rmi");
+{code}
+
+h2. Backup and migration
+
+You can also use the standalone server jar to backup existing repositories or to migrate them to a different configuration. The backup mode is activated with the {{--backup}} command line option. The essential command line options and their default values for the backup mode are:
+
+{code:none}
+$ java -jar jackrabbit-standalone-1.6.0.jar --backup \
+ --repo=jackrabbit \
+ --conf=jackrabbit/repository.xml \
+ --backup-repo=jackrabbit-backupN \
+ --backup-conf=jackrabbit-backupN/repository.xml
+{code}
+
+Note that the source repository must not be running when you use this feature. If the target repository already exist, then all content inside it is overwritten. Note also that the search indexes of the target repository will be generated only when the repository is next started. This keeps the disk size of the backup smaller, but causes a notable startup delay especially for large repositories if you need to restore that backup.
+
+To migrate a repository to a different configuration, simply point the {{--backup-conf}} option to a custom repository configuration file. Note that by default the backups are made using the default Jackrabbit repository configuration, regardless of the configuration of the source repository.
+
+h2. Drawbacks
+
+The Jackrabbit Standalone server is designed primarily as a quick and easy way to get a content repository up and running for testing and development purposes. For more complex deployment scenarios and configuration options you should look at the [Jackrabbit Web Application] and [Jackrabbit JCA Resource Adapter] packages.
+
+Note also that RMI remoting layer has not been optimized for performance, so currently the recommendation for accessing the JCR API in performance critical applications is to have the repository running locally in the same process as the client application.
Propchange: jackrabbit/site/trunk/content/standalone-server.cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/standalone-server.mdtext
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/standalone-server.mdtext?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/standalone-server.mdtext (added)
+++ jackrabbit/site/trunk/content/standalone-server.mdtext Tue Jan 10 18:50:59 2012
@@ -0,0 +1,197 @@
+Title: Standalone Server
+Each Jackrabbit release comes with a pre-built and runnable standalone
+server jar. It's the easiest way to get started with Jackrabbit, simply [download](downloads.html)
+ and start the jar to get a fully functional JCR content repository. The
+rest of this page documents what else you can do with the standalone
+server.
+
+{toc:minLevel=2}
+
+<a name="StandaloneServer-Runningthestandaloneserver"></a>
+## Running the standalone server
+
+You need Java version 5 or higher to run the Jackrabbit standalone server.
+To start the server, double-click on the standalone jar file, or invoke it
+on the command line.
+
+{code:none}
+$ java -jar jackrabbit-standalone-1.6.0.jar
+Welcome to Apache Jackrabbit!
+-------------------------------
+Using repository directory jackrabbit
+Writing log messages to jackrabbit/log
+Starting the server...
+Apache Jackrabbit is now running at http://localhost:8080/
+^C
+Shutting down the server...
+-------------------------------
+Goodbye from Apache Jackrabbit!
+
+
+ After staring the server, you can point your browser to [http://localhost:8080/]
+ to see Jackrabbit in action. Use the {{--port}} command line option to
+specify an alternative if the default port 8080 is already used by another
+program.
+ This is what the server should look like in your browser:
+
+ !standalone500.png|align=center!
+
+ By default the server will look for a content repository in the
+{{./jackrabbit}} directory and a repository configuration file in a
+{{repository.xml}} file within the repository directory. The repository
+directory is automatically created if it does not already exist, and a
+configuration file with the default configuration is created if no
+configuration is found.
+
+ Server, access, and repository log messages are written to log files in the
+{{log}} subdirectory within the repository directory.
+
+ You can stop the server by pressing {{Ctrl-C}} or by sending it a standard
+termination signal. The server will then close the content repository and
+exit cleanly.
+
+ h2. Command line options
+
+ You can customize the operation of the standalone server with the following
+command line options (with defaults in parenthesis).
+
+ {code:none}
+ $ java -jar jackrabbit-standalone-1.6.0.jar --help
+ usage: java -jar jackrabbit-standalone-1.6.0.jar [-?]
+ [-b]
+ [-c <arg>]
+ [-C
+ <arg>]
+ [-d]
+ [-f <arg>]
+ [-h <arg>]
+ [-l]
+ [-n]
+ [-p <arg>]
+ [-q]
+ [-r <arg>]
+ [-R
+ <arg>]
+ -?,--help print this message
+ -b,--backup create a backup of the repository
+ -c,--conf <arg> repository configuration file
+ -C,--backup-conf <arg> backup repository configuration file
+ -d,--debug enable debug logging
+ -f,--file <arg> location of this jar file
+ -h,--host <arg> IP address of the HTTP server
+ -l,--license print license information
+ -n,--notice print copyright notices
+ -p,--port <arg> TCP port of the HTTP server (8080)
+ -q,--quiet disable console output
+ -r,--repo <arg> repository directory (jackrabbit)
+ -R,--backup-repo <arg> backup repository directory (jackrabbit-backupN)
+
+
+You may want to increase the maximum amount of heap memory available to the
+Java virtual machine especially if you plan to have lots of concurrent
+clients accessing the repository or want to perform large batch operations.
+
+{code:none}
+$ java -Xmx256m -jar jackrabbit-standalone-1.6.0.jar
+
+
+ h2. Web interface
+
+ The web interface you see at [http://localhost:8080/]
+ is a simple web application built on top of the content repository. It
+contains some basic instructions on how to access the repository and comes
+with the following utility tools:
+
+ * Populate ([http://localhost:8080/populate.jsp]
+)
+ This tool populates the default workspace with example documents found on
+the web based on a Google search. This is an easy way to get some
+semi-random test content into the repository.
+ * Search ([http://localhost:8080/search.jsp]
+)
+ This tool uses the full text search feature to find content within the
+default workspace of the repository. To see the search feature in action,
+first add some content to the repository with the Populate tool and then
+try to search for the documents with the Search tool.
+ * Browse ([http://localhost:8080/repository/default/]
+)
+ The built-in WebDAV feature allows you to browse the file ({{nt:file}})
+and folder ({{nt:folder}}) nodes within the repository. See the WebDAV
+section below for all the other things you can do with this tool! Note that
+the server will by default accept any username and password combination.
+
+ h2. WebDAV access
+
+ The simple repository browser you can see at [http://localhost:8080/repository/default/]
+ is actually a fully featured WebDAV server backed by the content
+repository. You can mount this address as a WebDAV share to your normal
+filesystem and treat it as you would any shared network folder. This
+feature is especially useful for copying large amounts of files or folders
+to or from the repository. Note that this feature is limited to standard
+files and folders, any more fine-grained JCR content will simply not be
+visible.
+
+ The repository also exposes an alternative WebDAV access point at [http://localhost:8080/server/]
+ for more fine-grained content access. This access point implements a
+number of advanced WebDAV features that are not normally seen in plain
+file-based WebDAV servers. You will need a feature-rich WebDAV or HTTP
+client to access the full power of this interface. With the Jackrabbit
+spi2dav component you can even get full remote JCR access over the WebDAV
+features and some custom extensions available through this access point.
+
+ h2. RMI access
+
+ In addition to the WebDAV access points, the standalone server also
+supports remote JCR access over RMI. After adding the JCR API and the
+jackrabbit-jcr-rmi jars to your classpath, you can access the repository
+remotely with the following code:
+
+
+import org.apache.jackrabbit.rmi.repository.URLRemoteRepository;
+
+Repository repository =
+ new URLRemoteRepository("http://localhost:8080/rmi");
+
+
+ h2. Backup and migration
+
+ You can also use the standalone server jar to backup existing repositories
+or to migrate them to a different configuration. The backup mode is
+activated with the {{--backup}} command line option. The essential command
+line options and their default values for the backup mode are:
+
+ {code:none}
+ $ java -jar jackrabbit-standalone-1.6.0.jar --backup \
+ --repo=jackrabbit \
+ --conf=jackrabbit/repository.xml \
+ --backup-repo=jackrabbit-backupN \
+ --backup-conf=jackrabbit-backupN/repository.xml
+
+
+Note that the source repository must not be running when you use this
+feature. If the target repository already exist, then all content inside it
+is overwritten. Note also that the search indexes of the target repository
+will be generated only when the repository is next started. This keeps the
+disk size of the backup smaller, but causes a notable startup delay
+especially for large repositories if you need to restore that backup.
+
+To migrate a repository to a different configuration, simply point the
+*--backup-conf* option to a custom repository configuration file. Note
+that by default the backups are made using the default Jackrabbit
+repository configuration, regardless of the configuration of the source
+repository.
+
+<a name="StandaloneServer-Drawbacks"></a>
+## Drawbacks
+
+The Jackrabbit Standalone server is designed primarily as a quick and easy
+way to get a content repository up and running for testing and development
+purposes. For more complex deployment scenarios and configuration options
+you should look at the [Jackrabbit Web Application](jackrabbit-web-application.html)
+ and [Jackrabbit JCA Resource Adapter]
+ packages.
+
+Note also that RMI remoting layer has not been optimized for performance,
+so currently the recommendation for accessing the JCR API in performance
+critical applications is to have the repository running locally in the same
+process as the client application.
Propchange: jackrabbit/site/trunk/content/standalone-server.mdtext
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/supporting-software-attribution.cwiki
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/supporting-software-attribution.cwiki?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/supporting-software-attribution.cwiki (added)
+++ jackrabbit/site/trunk/content/supporting-software-attribution.cwiki Tue Jan 10 18:50:59 2012
@@ -0,0 +1 @@
+Developers use various tools to assist with their work, such as [IntelliJ IDEA|http://www.jetbrains.com/idea/opensource/] or [Eclipse|http://www.eclipse.org/]. Most tools do not require attribution, but some do ([YourKit Java Profiler|http://www.yourkit.com/]).
\ No newline at end of file
Propchange: jackrabbit/site/trunk/content/supporting-software-attribution.cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/supporting-software-attribution.mdtext
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/supporting-software-attribution.mdtext?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/supporting-software-attribution.mdtext (added)
+++ jackrabbit/site/trunk/content/supporting-software-attribution.mdtext Tue Jan 10 18:50:59 2012
@@ -0,0 +1,5 @@
+Title: Supporting software attribution
+Developers use various tools to assist with their work, such as [IntelliJ IDEA](http://www.jetbrains.com/idea/opensource/)
+ or [Eclipse|http://www.eclipse.org/]
+. Most tools do not require attribution, but some do ([YourKit Java
+Profiler|http://www.yourkit.com/]).
Propchange: jackrabbit/site/trunk/content/supporting-software-attribution.mdtext
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/website.cwiki
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/website.cwiki?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/website.cwiki (added)
+++ jackrabbit/site/trunk/content/website.cwiki Tue Jan 10 18:50:59 2012
@@ -0,0 +1,8 @@
+The [Apache Jackrabbit website|http://jackrabbit.apache.org/] is managed using the [JCR space|http://cwiki.apache.org/confluence/display/JCR] in the [Confluence wiki|http://cwiki.apache.org/CWIKI/] at Apache.
+
+Only [Jackrabbit committers|Jackrabbit Team] are allowed to modify the site content. To edit the site content you need to register for a Confluence account and ask one of the Confluence admins (currently Jukka and Felix) to add you to the Jackrabbit group.
+
+The contents of the wiki are automatically exported and synchronized to the public web server every few hours. The auto-export configuration (including the site template) is available in the "Administration" section of Confluence. See the [CWIKI page|http://cwiki.apache.org/CWIKI/] for more details about the auto-export process.
+
+In addition to the wiki pages and their attachments the Jackrabbit site also contains static content like API documentation and stylesheets. This content is managed using the [site tree|https://svn.apache.org/repos/asf/jackrabbit/site/] in Subversion. The static site content is automatically updated along with the auto-exported wiki content.
+
Propchange: jackrabbit/site/trunk/content/website.cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/website.mdtext
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/website.mdtext?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/website.mdtext (added)
+++ jackrabbit/site/trunk/content/website.mdtext Tue Jan 10 18:50:59 2012
@@ -0,0 +1,23 @@
+Title: Website
+The [Apache Jackrabbit website](http://jackrabbit.apache.org/)
+ is managed using the [JCR space|http://cwiki.apache.org/confluence/display/JCR]
+ in the [Confluence wiki|http://cwiki.apache.org/CWIKI/]
+ at Apache.
+
+Only [Jackrabbit committers](jackrabbit-team.html)
+ are allowed to modify the site content. To edit the site content you need
+to register for a Confluence account and ask one of the Confluence admins
+(currently Jukka and Felix) to add you to the Jackrabbit group.
+
+The contents of the wiki are automatically exported and synchronized to the
+public web server every few hours. The auto-export configuration (including
+the site template) is available in the "Administration" section of
+Confluence. See the [CWIKI page](http://cwiki.apache.org/CWIKI/)
+ for more details about the auto-export process.
+
+In addition to the wiki pages and their attachments the Jackrabbit site
+also contains static content like API documentation and stylesheets. This
+content is managed using the [site tree](https://svn.apache.org/repos/asf/jackrabbit/site/)
+ in Subversion. The static site content is automatically updated along with
+the auto-exported wiki content.
+
Propchange: jackrabbit/site/trunk/content/website.mdtext
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.cwiki
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.cwiki?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.cwiki (added)
+++ jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.cwiki Tue Jan 10 18:50:59 2012
@@ -0,0 +1,59 @@
+{HTMLcomment:hidden}[!Jackrabbit-Download-2.2.5.png|align=right!|Downloads]{HTMLcomment}
+The Apache Jackrabbit⢠content repository is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in [JSR 170|http://jcp.org/en/jsr/detail?id=170|Java Specification Request 170, JCR 1.0] and [283|http://jcp.org/en/jsr/detail?id=283|Java Specification Request 283, JCR 2.0]).
+
+A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more.
+
+Apache Jackrabbit is a project of the [Apache Software Foundation|http://www.apache.org/].
+
+h2. Apache Jackrabbit News
+
+*January 2nd, 2012: Apache Jackrabbit 2.3.6 released*
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features and other improvements.
+See the [downloads page|Downloads#v23] for more details.
+
+*December 16th, 2011: Apache Jackrabbit 2.3.5 released*
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features and other improvements.
+
+*November 29th, 2011: Apache Jackrabbit 2.3.4 released*
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features and other improvements.
+
+*November 22nd, 2011: Apache Jackrabbit 2.2.10 released*
+Apache Jackrabbit 2.2.10 is patch release that contains fixes and improvements over previous 2.2.x releases. See the [downloads page|Downloads#v22] for more details.
+
+*November 15th, 2011: Apache Jackrabbit 2.3.3 released*
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features and other improvements.
+
+*November 2nd, 2011: Apache Jackrabbit 2.3.2 released*
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features and other improvements.
+
+*October 3rd, 2011: Apache Jackrabbit 2.3.0 released*
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features and other improvements.
+
+*October 3rd, 2011: End of life of Jackrabbit 1.x*
+The 1.6.5 patch release marks the end of active maintenance of Jackrabbit 1.x. All users are encouraged to upgrade to the more recent Jackrabbit 2.x versions.
+
+*October 3rd, 2011: Apache Jackrabbit 2.2.9, 2.1.6, 2.0.5 and 1.6.5 released*
+These patch releases contain fixes and improvements over previous releases. See the [downloads page|Downloads] for more details.
+
+*August 23, 2011: Apache Jackrabbit 2.2.8 released*
+Apache Jackrabbit 2.2.8 is patch release that contains fixes and improvements over previous 2.2.x releases.
+
+*June 7, 2011: Apache Jackrabbit 2.2.7 released*
+Apache Jackrabbit 2.2.7 is patch release that contains fixes and improvements over previous 2.2.x releases.
+
+*June 7, 2011: Apache Jackrabbit 2.1.5 released*
+Apache Jackrabbit 2.1.5 is patch release that fixes issues reported against previous releases.
+
+*March 18, 2011: Apache Jackrabbit 2.2.5 released*
+Apache Jackrabbit 2.2.5 is patch release that contains fixes and improvements over previous 2.2.x releases.
+
+*February 15, 2011: Apache Jackrabbit 2.2.4 released*
+Apache Jackrabbit 2.2.4 is patch release that contains fixes and improvements over previous 2.2.x releases.
+
+*January 26, 2011: Apache Jackrabbit 2.2.2 released*
+Apache Jackrabbit 2.2.2 is patch release that contains fixes and improvements over previous 2.2.x releases.
+
+*January 11, 2011: Apache Jackrabbit 2.2.1 released*
+Apache Jackrabbit 2.2.1 is patch release that contains fixes and improvements over Jackrabbit 2.2.0.
+
+See the [news archive|News archive] for past news.
\ No newline at end of file
Propchange: jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.mdtext
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.mdtext?rev=1229679&view=auto
==============================================================================
--- jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.mdtext (added)
+++ jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.mdtext Tue Jan 10 18:50:59 2012
@@ -0,0 +1,104 @@
+Title: Welcome to Apache Jackrabbit
+Notice: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ .
+ http://www.apache.org/licenses/LICENSE-2.0
+ .
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+Welcome to Apache Jackrabbit
+============================
+
+{HTMLcomment:hidden}[!Jackrabbit-Download-2.2.5.png](align=right!.html "Downloads")The Apache Jackrabbit⢠content repository is a fully conforming
+implementation of the Content Repository for Java Technology API (JCR,
+specified in [JSR 170|http://jcp.org/en/jsr/detail?id=170|Java Specification Request 170, JCR 1.0]
+ and [283|http://jcp.org/en/jsr/detail?id=283|Java Specification Request 283, JCR 2.0]
+).
+
+A content repository is a hierarchical content store with support for
+structured and unstructured content, full text search, versioning,
+transactions, observation, and more.
+
+Apache Jackrabbit is a project of the [Apache Software Foundation](http://www.apache.org/)
+<a name="WelcometoApacheJackrabbit-ApacheJackrabbitNews"></a>
+## Apache Jackrabbit News
+
+**January 2nd, 2012: Apache Jackrabbit 2.3.6 released**
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from
+Jackrabbit trunk, with a focus on new features and other improvements.
+See the [downloads page](downloads#v23.html)
+**December 16th, 2011: Apache Jackrabbit 2.3.5 released**
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from
+Jackrabbit trunk, with a focus on new features and other improvements.
+
+**November 29th, 2011: Apache Jackrabbit 2.3.4 released**
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from
+Jackrabbit trunk, with a focus on new features and other improvements.
+
+**November 22nd, 2011: Apache Jackrabbit 2.2.10 released**
+Apache Jackrabbit 2.2.10 is patch release that contains fixes and
+improvements over previous 2.2.x releases. See the [downloads page|Downloads#v22]
+ for more details.
+
+**November 15th, 2011: Apache Jackrabbit 2.3.3 released**
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from
+Jackrabbit trunk, with a focus on new features and other improvements.
+
+**November 2nd, 2011: Apache Jackrabbit 2.3.2 released**
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from
+Jackrabbit trunk, with a focus on new features and other improvements.
+
+**October 3rd, 2011: Apache Jackrabbit 2.3.0 released**
+Apache Jackrabbit 2.3 is an unstable series of releases cut directly from
+Jackrabbit trunk, with a focus on new features and other improvements.
+
+**October 3rd, 2011: End of life of Jackrabbit 1.x**
+The 1.6.5 patch release marks the end of active maintenance of Jackrabbit
+1.x. All users are encouraged to upgrade to the more recent Jackrabbit 2.x
+versions.
+
+*October 3rd, 2011: Apache Jackrabbit 2.2.9, 2.1.6, 2.0.5 and 1.6.5
+released*
+These patch releases contain fixes and improvements over previous releases.
+See the [downloads page|Downloads]
+ for more details.
+
+**August 23, 2011: Apache Jackrabbit 2.2.8 released**
+Apache Jackrabbit 2.2.8 is patch release that contains fixes and
+improvements over previous 2.2.x releases.
+
+**June 7, 2011: Apache Jackrabbit 2.2.7 released**
+Apache Jackrabbit 2.2.7 is patch release that contains fixes and
+improvements over previous 2.2.x releases.
+
+**June 7, 2011: Apache Jackrabbit 2.1.5 released**
+Apache Jackrabbit 2.1.5 is patch release that fixes issues reported against
+previous releases.
+
+**March 18, 2011: Apache Jackrabbit 2.2.5 released**
+Apache Jackrabbit 2.2.5 is patch release that contains fixes and
+improvements over previous 2.2.x releases.
+
+**February 15, 2011: Apache Jackrabbit 2.2.4 released**
+Apache Jackrabbit 2.2.4 is patch release that contains fixes and
+improvements over previous 2.2.x releases.
+
+**January 26, 2011: Apache Jackrabbit 2.2.2 released**
+Apache Jackrabbit 2.2.2 is patch release that contains fixes and
+improvements over previous 2.2.x releases.
+
+**January 11, 2011: Apache Jackrabbit 2.2.1 released**
+Apache Jackrabbit 2.2.1 is patch release that contains fixes and
+improvements over Jackrabbit 2.2.0.
+
+See the [news archive](news-archive.html)
\ No newline at end of file
Propchange: jackrabbit/site/trunk/content/welcome-to-apache-jackrabbit.mdtext
------------------------------------------------------------------------------
svn:eol-style = native