Author: buildbot
Date: Mon Dec 7 14:14:54 2015
New Revision: 974842
Log:
Staging update by buildbot for shindig
Modified:
websites/staging/shindig/trunk/content/ (props changed)
websites/staging/shindig/trunk/content/about_shindig_getting_started.html
websites/staging/shindig/trunk/content/about_shindig_overview.html
websites/staging/shindig/trunk/content/code_conventions.html
websites/staging/shindig/trunk/content/community_overview.html
websites/staging/shindig/trunk/content/documentation_building_java.html
websites/staging/shindig/trunk/content/documentation_building_php.html
websites/staging/shindig/trunk/content/documentation_centre.html
websites/staging/shindig/trunk/content/documentation_features.html
websites/staging/shindig/trunk/content/documentation_java.html
websites/staging/shindig/trunk/content/documentation_php.html
websites/staging/shindig/trunk/content/documentation_website.html
websites/staging/shindig/trunk/content/download.html
websites/staging/shindig/trunk/content/faq.html
websites/staging/shindig/trunk/content/getting-help.html
websites/staging/shindig/trunk/content/index.html
websites/staging/shindig/trunk/content/issue-tracking.html
websites/staging/shindig/trunk/content/jira_conventions.html
websites/staging/shindig/trunk/content/license.html
websites/staging/shindig/trunk/content/mail-lists.html
websites/staging/shindig/trunk/content/powered-by.html
websites/staging/shindig/trunk/content/releasing.html
websites/staging/shindig/trunk/content/resources.html
websites/staging/shindig/trunk/content/security.html
websites/staging/shindig/trunk/content/source-repository.html
websites/staging/shindig/trunk/content/svn_conventions.html
Propchange: websites/staging/shindig/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 7 14:14:54 2015
@@ -1 +1 @@
-1718361
+1718369
Modified:
websites/staging/shindig/trunk/content/about_shindig_getting_started.html
==============================================================================
--- websites/staging/shindig/trunk/content/about_shindig_getting_started.html
(original)
+++ websites/staging/shindig/trunk/content/about_shindig_getting_started.html
Mon Dec 7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,9 +180,20 @@
</div>
<div class="container">
- <h1 id="getting-started">Getting Started</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="getting-started">Getting Started<a class="headerlink"
href="#getting-started" title="Permanent link">¶</a></h1>
<p>So, you correctly <a href="download.html">downloaded</a> and <a
href="download.html">installed</a> Apache Shindig, what's next?</p>
-<h2 id="discovering-apache-shindig-samples">Discovering Apache Shindig
Samples</h2>
+<h2 id="discovering-apache-shindig-samples">Discovering Apache Shindig
Samples<a class="headerlink" href="#discovering-apache-shindig-samples"
title="Permanent link">¶</a></h2>
<p>The sample container should be your first starting point:</p>
<p><a
href="http://localhost:8080/containers/commoncontainer/index.html";>http://localhost:8080/containers/commoncontainer/index.html</a></p>
<p>The page displayed in the figure bellow is the Apache Shindig sample
container. Its goal is to help you to deploy and test your
Modified: websites/staging/shindig/trunk/content/about_shindig_overview.html
==============================================================================
--- websites/staging/shindig/trunk/content/about_shindig_overview.html
(original)
+++ websites/staging/shindig/trunk/content/about_shindig_overview.html Mon Dec
7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,12 +180,23 @@
</div>
<div class="container">
- <h1 id="introduction">Introduction</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h1>
<p>Apache Shindig, a word meaning party, was originally started by Google in
2007 as a reference container for hosting OpenSocial
compatible widgets in any website. Originally a port of Google's iGoogle
gadget container, with Brian McCallister's PHP code,
Apache Shindig threw off it's egg shell, and showed that Google was serious
about making OpenSocial accessible to a larger
number of sites. Since December 2007, Apache Shindig is now an Apache
project.</p>
-<h1 id="apache-shindigs-objectives">Apache Shindig's Objectives</h1>
+<h1 id="apache-shindigs-objectives">Apache Shindig's Objectives<a
class="headerlink" href="#apache-shindigs-objectives" title="Permanent
link">¶</a></h1>
<div class="row-fluid">
<div class="span7">
Apache Shindig's primary goal is to provide infrastructure for those
wishing to host OpenSocial apps on their websites.
@@ -195,8 +208,8 @@ number of sites. Since December 2007, Ap
</div>
</div>
-<h1 id="apache-shindig-components">Apache Shindig Components</h1>
-<h2 id="server-side">Server Side</h2>
+<h1 id="apache-shindig-components">Apache Shindig Components<a
class="headerlink" href="#apache-shindig-components" title="Permanent
link">¶</a></h1>
+<h2 id="server-side">Server Side<a class="headerlink" href="#server-side"
title="Permanent link">¶</a></h2>
<p>The Java version of Apache Shindig have 3 major server side components:</p>
<ol>
<li>Persistent Data Loading Mechanism.</li>
@@ -214,7 +227,7 @@ number of sites. Since December 2007, Ap
</div>
</div>
-<h2 id="client-side">Client Side</h2>
+<h2 id="client-side">Client Side<a class="headerlink" href="#client-side"
title="Permanent link">¶</a></h2>
<p>The Javascript features are:</p>
<ul>
<li>Gadget container (gadget.js), fully OpenSocial gadget compliant.</li>
@@ -229,9 +242,9 @@ number of sites. Since December 2007, Ap
</div>
</div>
-<h2 id="put-it-together-opensocial-flow">Put It Together: OpenSocial Flow</h2>
+<h2 id="put-it-together-opensocial-flow">Put It Together: OpenSocial Flow<a
class="headerlink" href="#put-it-together-opensocial-flow" title="Permanent
link">¶</a></h2>
<p>The following is a typical flow to get a list of Friends.</p>
-<h3 id="server-side-flow">Server Side Flow</h3>
+<h3 id="server-side-flow">Server Side Flow<a class="headerlink"
href="#server-side-flow" title="Permanent link">¶</a></h3>
<ol>
<li>Call JsonRpcServlet.</li>
<li>Get the appropriate handler.</li>
@@ -247,13 +260,13 @@ number of sites. Since December 2007, Ap
<li>Get the JSON object from the DB.</li>
<li>Return to the client.</li>
</ol>
-<h3 id="client-side-flow">Client Side Flow</h3>
+<h3 id="client-side-flow">Client Side Flow<a class="headerlink"
href="#client-side-flow" title="Permanent link">¶</a></h3>
<ol>
<li>Create request object.</li>
<li>Populate request parameters.</li>
<li>Send the request.</li>
</ol>
-<h2 id="opensocial-apis">OpenSocial APIs</h2>
+<h2 id="opensocial-apis">OpenSocial APIs<a class="headerlink"
href="#opensocial-apis" title="Permanent link">¶</a></h2>
<p>Apache Shindig implements several OpenSocial APIs:</p>
<ul>
<li>OpenSocial REST: for server to server communication</li>
@@ -261,7 +274,7 @@ number of sites. Since December 2007, Ap
<li>Javascript: for gadgets</li>
</ul>
<p>For more information on the OpenSocial APIs see the <a
href="https://opensocial.atlassian.net/wiki/display/OSD/Specs";>OpenSocial
spec</a>.</p>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources"
title="Permanent link">¶</a></h2>
<ul>
<li><a
href="https://sites.google.com/site/opensocialarticles/Home/shindig-rest-java";>Overview
of REST Implementation in Apache Shindig - Java Version</a> by Rajdeep
Dua.</li>
<li><a
href="https://sites.google.com/site/opensocialarticles/shindig-architecture-presentation";>Presentation
on Shindig Architecture - Java</a> by Rajdeep Dua.</li>
Modified: websites/staging/shindig/trunk/content/code_conventions.html
==============================================================================
--- websites/staging/shindig/trunk/content/code_conventions.html (original)
+++ websites/staging/shindig/trunk/content/code_conventions.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,10 +180,21 @@
</div>
<div class="container">
- <h1 id="apache-shindig-code-style-and-code-conventions">Apache
Shindig Code Style And Code Conventions</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apache-shindig-code-style-and-code-conventions">Apache Shindig Code
Style And Code Conventions<a class="headerlink"
href="#apache-shindig-code-style-and-code-conventions" title="Permanent
link">¶</a></h1>
<p>This document describes how developers and contributors should write code.
The reasoning
of these styles and conventions is mainly for consistency, readability and
maintainability reasons.</p>
-<h2 id="generic-code-style-and-convention">Generic Code Style And
Convention</h2>
+<h2 id="generic-code-style-and-convention">Generic Code Style And Convention<a
class="headerlink" href="#generic-code-style-and-convention" title="Permanent
link">¶</a></h2>
<p>All working files (java, xml, others) should respect the following
conventions:</p>
<ul>
<li>License Header: Always add the current
@@ -195,12 +208,12 @@ use the <a href="http://andrei.gmxhome.d
<li>Line wrapping: Always use a 100-column line width.</li>
</ul>
<p>Note: The specific styles and conventions, listed in the next sections,
could override these generic rules.</p>
-<h2 id="java">Java</h2>
-<h3 id="java-code-style">Java Code Style</h3>
+<h2 id="java">Java<a class="headerlink" href="#java" title="Permanent
link">¶</a></h2>
+<h3 id="java-code-style">Java Code Style<a class="headerlink"
href="#java-code-style" title="Permanent link">¶</a></h3>
<p>The full Apache Shindig for Java is described in our
<a href="http://cwiki.apache.org/SHINDIGxSITE/java-style.html";>Wiki</a>.</p>
<p><span class="label label-important">Describe how to import Eclipse Java
code templates</span></p>
-<h2 id="javascript">JavaScript</h2>
+<h2 id="javascript">JavaScript<a class="headerlink" href="#javascript"
title="Permanent link">¶</a></h2>
<p><span class="label label-important">Describe how to import Eclipse
JavaScript code templates</span></p>
<hr>
Modified: websites/staging/shindig/trunk/content/community_overview.html
==============================================================================
--- websites/staging/shindig/trunk/content/community_overview.html (original)
+++ websites/staging/shindig/trunk/content/community_overview.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,16 +180,27 @@
</div>
<div class="container">
- <div class="codehilite"><pre>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<div class="codehilite"><pre>
</pre></div>
-<h1 id="overview">Overview</h1>
+<h1 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h1>
<p>Apache Shindig, like any other opensource project, relies heavily on the
efforts of the entire user community to
be ever vigilant for improvements, logging of defects, communicating
use-cases, generating documentation, and being wary
of other users in need. This is a quick guide outlining what members of the
Apache Shindig community may do to make the
system work better for everyone.</p>
-<h2 id="why-would-i-want-to-help">Why Would I Want To Help?</h2>
+<h2 id="why-would-i-want-to-help">Why Would I Want To Help?<a
class="headerlink" href="#why-would-i-want-to-help" title="Permanent
link">¶</a></h2>
<p>There are several reasons these are good things.</p>
<ul>
<li>By answering other people's questions, you can learn more for yourself</li>
@@ -195,7 +208,7 @@ system work better for everyone.</p>
<li>By reporting issues, you ensure that bugs don't get missed, or
forgotten</li>
<li>You are giving back to a community that has given you software for
free</li>
</ul>
-<h2 id="how-to-contribute">How to contribute?</h2>
+<h2 id="how-to-contribute">How to contribute?<a class="headerlink"
href="#how-to-contribute" title="Permanent link">¶</a></h2>
<p>As with any open source project, there are several ways you can help:</p>
<ul>
<li>Join the <a href="mail-lists.html">mailing list</a> and answer other
user's questions</li>
@@ -208,7 +221,7 @@ submitting patches to correct it. You ca
collate and organize information that is already there.</li>
</ul>
<p><strong>Your participation in the community is much
appreciated!</strong></p>
-<h2 id="create-and-submitting-a-patch">Create and submitting a patch</h2>
+<h2 id="create-and-submitting-a-patch">Create and submitting a patch<a
class="headerlink" href="#create-and-submitting-a-patch" title="Permanent
link">¶</a></h2>
<p><strong>Note:</strong> Be sure to respect our Java code style! You could
also read this thread
<a
href="http://markmail.org/message/t6b7jgzvfjj4fiqu";>http://markmail.org/message/t6b7jgzvfjj4fiqu</a>.</p>
<p>For new people to the project, creating patches is the way to get started
and build your reputation.</p>
@@ -245,13 +258,13 @@ collate and organize information that is
in which case you'll get the updates on the issue without needing to
"Watch" them individually.</li>
<li>After your patch is reviewed and the community deems it acceptable a
committer will commit the code to SVN.</li>
</ol>
-<h2 id="how-do-i-join-the-project">How do I join the Project?</h2>
+<h2 id="how-do-i-join-the-project">How do I join the Project?<a
class="headerlink" href="#how-do-i-join-the-project" title="Permanent
link">¶</a></h2>
<p>Projects at Apache operate under a <a
href="http://www.apache.org/foundation/how-it-works.html#meritocracy";>meritocracy</a>,
meaning those that the developers notice participating to a high extent will
be invited to join the project as a committer.</p>
<p>This is as much based on personality and ability to work with other
developers and the community as it is with proven
technical ability. Being unhelpful to other users, or obviously looking to
become a committer for bragging rights and
nothing else is frowned upon, as is asking to be made a committer without
having contributed sufficiently to be invited.</p>
-<h2 id="developer-conventions">Developer Conventions</h2>
+<h2 id="developer-conventions">Developer Conventions<a class="headerlink"
href="#developer-conventions" title="Permanent link">¶</a></h2>
<p>There are a number of conventions used in the project, which contributors
and developers alike should follow for
consistency's sake.</p>
<ul>
@@ -259,11 +272,11 @@ consistency's sake.</p>
<li><a href="jira_conventions.html">JIRA Conventions</a></li>
<li><a href="svn_conventions.html">SVN Conventions</a></li>
</ul>
-<h2 id="developer-documentation">Developer Documentation</h2>
+<h2 id="developer-documentation">Developer Documentation<a class="headerlink"
href="#developer-documentation" title="Permanent link">¶</a></h2>
<ul>
<li><a href="releasing.html">Apache Shindig Release Process</a></li>
</ul>
-<h2 id="apache-resources">Apache Resources</h2>
+<h2 id="apache-resources">Apache Resources<a class="headerlink"
href="#apache-resources" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.apache.org/foundation/";>About the Apache Software
Foundation</a></li>
<li><a href="http://www.apache.org/dev/";>Developer Resources</a></li>
Modified:
websites/staging/shindig/trunk/content/documentation_building_java.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_building_java.html
(original)
+++ websites/staging/shindig/trunk/content/documentation_building_java.html Mon
Dec 7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="building-and-running-apache-shindig-for-java">Building and
Running Apache Shindig for Java</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="building-and-running-apache-shindig-for-java">Building and Running
Apache Shindig for Java<a class="headerlink"
href="#building-and-running-apache-shindig-for-java" title="Permanent
link">¶</a></h1>
<p>This is the Java steps on how to build and run Apache Shindig.</p>
<ul>
<li>Prequisites</li>
@@ -189,7 +202,7 @@
<li>Running inside Eclipse</li>
<li>Running with Caja</li>
</ul>
-<h2 id="prequisites-before-building-apache-shindig">Prequisites before
building Apache Shindig</h2>
+<h2 id="prequisites-before-building-apache-shindig">Prequisites before
building Apache Shindig<a class="headerlink"
href="#prequisites-before-building-apache-shindig" title="Permanent
link">¶</a></h2>
<p>In order to build Apache Shindig, you must have the following:</p>
<ul>
<li>Java (JDK/JRE) 1.5 or later installed on your system and the JAVA_HOME
environment variable set.<ul>
@@ -205,14 +218,14 @@
</ul>
</li>
</ul>
-<h2 id="getting-the-code">Getting the code</h2>
+<h2 id="getting-the-code">Getting the code<a class="headerlink"
href="#getting-the-code" title="Permanent link">¶</a></h2>
<p>Create a subdirectory and checkout the Apache Shindig code from its
Subversion repository</p>
<ol>
<li>mkdir ~/src/shindig (or wherever you'd like to put it)</li>
<li>cd ~/src/shindig</li>
<li>svn co http://svn.apache.org/repos/asf/shindig/trunk/</li>
</ol>
-<h2 id="building-and-running-the-code-with-maven">Building and running the
code with Maven</h2>
+<h2 id="building-and-running-the-code-with-maven">Building and running the
code with Maven<a class="headerlink"
href="#building-and-running-the-code-with-maven" title="Permanent
link">¶</a></h2>
<p>To build a Web Archive (WAR) file for the Gadget server and run tests,
perform the following:</p>
<ol>
<li>Make sure you have the prerequisites installed first.</li>
@@ -246,7 +259,7 @@
</div>
</div>
-<h2 id="setting-up-an-eclipse-development-environment">Setting up an Eclipse
development environment</h2>
+<h2 id="setting-up-an-eclipse-development-environment">Setting up an Eclipse
development environment<a class="headerlink"
href="#setting-up-an-eclipse-development-environment" title="Permanent
link">¶</a></h2>
<ol>
<li>Download and unzip the Eclipse IDE for Java EE Developers from the <a
href="http://eclipse.org/downloads/";>Eclipse downloads page</a>. At the time
that this tutorial was written Eclipse Indigo is the current release. </li>
<li>Download and unzip Apache Maven from the <a
href="http://maven.apache.org/download.html";>Maven downloads page</a>. At the
time that this tutorial was written Maven 3.0.3 is the current release.</li>
@@ -315,14 +328,14 @@
<li>Click the Tomcat server in the server view and select the Debug icon.</li>
<li>Open a browser and navigate to <a
href="http://localhost:8080/samplecontainer/examples/commoncontainer/index.html";>http://localhost:8080/samplecontainer/examples/commoncontainer/index.html</a>
and render some gadgets!</li>
</ol>
-<h2 id="generating-code-coverage-in-eclipse">Generating Code Coverage in
Eclipse</h2>
+<h2 id="generating-code-coverage-in-eclipse">Generating Code Coverage in
Eclipse<a class="headerlink" href="#generating-code-coverage-in-eclipse"
title="Permanent link">¶</a></h2>
<p>To generate code coverage statistics inside of Eclipse, install the <a
href="https://cwiki.apache.org/WICKET/maven-jetty-plugin.html";>EclEmma
plugin</a>. Then</p>
<ul>
<li>"Using eclipse external tools"</li>
<li>"Attaching to the server running in debug mode, using eclipse"</li>
</ul>
<p><b>Note:</b> You must have set up Eclipse to build the code or do mvn
package yourself after making changes, but you won't need to restart Jetty to
see your changes.</p>
-<h2 id="running-with-caja">Running with Caja</h2>
+<h2 id="running-with-caja">Running with Caja<a class="headerlink"
href="#running-with-caja" title="Permanent link">¶</a></h2>
<p>Caja is an important part of OpenSocial that greatly enhances JavaScript
security. Caja is managed in a separate open
source project hosted by Google code projects. For more information on Caja,
see:
<a
href="http://code.google.com/p/google-caja/wiki/CajaEasyIntro";>http://code.google.com/p/google-caja/wiki/CajaEasyIntro</a></p>
@@ -331,7 +344,7 @@ source project hosted by Google code pro
<li>Point it to this gadget: <a
href="http://localhost:8080/gadgets/files/samplecontainer/examples/SocialHelloWorld.xml";>http://localhost:8080/gadgets/files/samplecontainer/examples/SocialHelloWorld.xml</a></li>
</ol>
<p>To see the cajoled code (Firefox only), right-click inside the iframe and
do "This Frame -> View Frame Source"</p>
-<h2 id="additional-reading">Additional reading</h2>
+<h2 id="additional-reading">Additional reading<a class="headerlink"
href="#additional-reading" title="Permanent link">¶</a></h2>
<p>Read <a
href="http://svn.apache.org/repos/asf/shindig/trunk/java/README";>java/README</a>
for original instructions on how to start up any of the java shindig
servers.</p>
<p>Read <a
href="http://svn.apache.org/repos/asf/shindig/trunk/features/README";>javascript/README</a>
for instructions for using the Apache Shindig Gadget Container JavaScript to
enable your page to render Gadgets using gmodules.com or a server started up as
described above.</p>
<hr>
Modified: websites/staging/shindig/trunk/content/documentation_building_php.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_building_php.html
(original)
+++ websites/staging/shindig/trunk/content/documentation_building_php.html Mon
Dec 7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="building-and-running-apache-shindig-for-php">Building and
running Apache Shindig for PHP</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="building-and-running-apache-shindig-for-php">Building and running
Apache Shindig for PHP<a class="headerlink"
href="#building-and-running-apache-shindig-for-php" title="Permanent
link">¶</a></h1>
<p><br/>
<span class="alert alert-error">The PHP version of Shindig has been moved to
the attic, this is only kept here for
legacy reasons.</span></p>
@@ -189,7 +202,7 @@ legacy reasons.</span></p>
<li>Running Apache Shindig</li>
<li>Additonal reading</li>
</ul>
-<h2 id="prequisites-before-building-apache-shindig-for-php">Prequisites before
building Apache Shindig for PHP</h2>
+<h2 id="prequisites-before-building-apache-shindig-for-php">Prequisites before
building Apache Shindig for PHP<a class="headerlink"
href="#prequisites-before-building-apache-shindig-for-php" title="Permanent
link">¶</a></h2>
<p>In order to build and run Apache Shindig for PHP, you must have the
following:</p>
<ul>
<li>A Subversion client installed in order to checkout the code.<ul>
@@ -202,7 +215,7 @@ legacy reasons.</span></p>
</ul>
</li>
</ul>
-<h2 id="getting-the-code">Getting the code</h2>
+<h2 id="getting-the-code">Getting the code<a class="headerlink"
href="#getting-the-code" title="Permanent link">¶</a></h2>
<p>Create a subdirectory in your web document root, e.g. /var/www/html and
checkout the
Apache Shindig code from its Subversion repository.</p>
<ol>
@@ -210,10 +223,10 @@ Apache Shindig code from its Subversion
<li>cd /var/www/html/shindig</li>
<li>svn co http://svn.apache.org/repos/asf/shindig/trunk/</li>
</ol>
-<h2 id="running-apache-shindig">Running Apache Shindig</h2>
+<h2 id="running-apache-shindig">Running Apache Shindig<a class="headerlink"
href="#running-apache-shindig" title="Permanent link">¶</a></h2>
<p>With PHP There is no need to build anything - the source code is already
built.</p>
<p>To run the code, you have several options:</p>
-<h3 id="a-create-a-new-virtual-host">a. Create a new virtual host</h3>
+<h3 id="a-create-a-new-virtual-host">a. Create a new virtual host<a
class="headerlink" href="#a-create-a-new-virtual-host" title="Permanent
link">¶</a></h3>
<p>Point your apache to the php dir with a virtual host like:</p>
<pre>
<VirtualHost your_ip:your_port>
@@ -237,7 +250,7 @@ Apache Shindig code from its Subversion
</div>
</div>
-<h3 id="b-run-with-an-existing-host">b. Run with an existing host</h3>
+<h3 id="b-run-with-an-existing-host">b. Run with an existing host<a
class="headerlink" href="#b-run-with-an-existing-host" title="Permanent
link">¶</a></h3>
<p>If you cannot/don't want to create a virtual host, you can edit the file
php/config.php and
change the web_prefix setting to '/shindig/php'.</p>
<p>Then you can run the gadget by pointing your browser to:</p>
@@ -254,7 +267,7 @@ change the web_prefix setting to '/shind
</div>
</div>
-<h2 id="additional-reading">Additional reading</h2>
+<h2 id="additional-reading">Additional reading<a class="headerlink"
href="#additional-reading" title="Permanent link">¶</a></h2>
<p>Read <a
href="http://svn.apache.org/repos/asf/shindig/trunk/php/README";>php/README</a>
for original instructions on
how to start up the php Apache Shindig server.</p>
<hr>
Modified: websites/staging/shindig/trunk/content/documentation_centre.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_centre.html (original)
+++ websites/staging/shindig/trunk/content/documentation_centre.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="documentation-center">Documentation Center</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="documentation-center">Documentation Center<a class="headerlink"
href="#documentation-center" title="Permanent link">¶</a></h1>
<p>This documentation center provides information for developers who wants to
develop using Apache Shindig. </p>
<p>In addition to documentation on Java you could also read about the features
Shindig uses, how to
update the website, and how to perform a release.</p>
Modified: websites/staging/shindig/trunk/content/documentation_features.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_features.html
(original)
+++ websites/staging/shindig/trunk/content/documentation_features.html Mon Dec
7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1
id="documentation-centre-for-the-apache-shindigs-features">Documentation Centre
for the Apache Shindig's Features</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="documentation-centre-for-the-apache-shindigs-features">Documentation
Centre for the Apache Shindig's Features<a class="headerlink"
href="#documentation-centre-for-the-apache-shindigs-features" title="Permanent
link">¶</a></h1>
<p>This documentation centre is for developer who wants to use the Apache
Shindig's features.</p>
<ul>
<li>Features List</li>
@@ -186,7 +199,7 @@
<li>Create Your Own Feature</li>
<li>JavascriptDoc for 1.1.x</li>
</ul>
-<h2 id="apache-shindig-features">Apache Shindig Features</h2>
+<h2 id="apache-shindig-features">Apache Shindig Features<a class="headerlink"
href="#apache-shindig-features" title="Permanent link">¶</a></h2>
<p>A list of features can be found in the source code.</p>
<ul>
<li><a
href="https://svn.apache.org/repos/asf/shindig/tags/shindig-project-2.5.0/features/src/main/javascript/features/";>Shindig
2.5.0</a></li>
@@ -195,7 +208,7 @@
<li><a
href="https://svn.apache.org/repos/asf/shindig/tags/shindig-project-2.0.0/features/src/main/javascript/features/";>Shindig
2.0.0</a></li>
<li><a
href="https://svn.apache.org/repos/asf/shindig/tags/shindig-project-1.0.1/features/src/main/javascript/features/";>Shindig
1.0.1</a></li>
</ul>
-<h2 id="using-features">Using Features</h2>
+<h2 id="using-features">Using Features<a class="headerlink"
href="#using-features" title="Permanent link">¶</a></h2>
<p>To use an above feature in your gadget, you need to specify the feature as
<require/> in <ModulePrefs/> and defining
some Javascript codes to use it.</p>
<p>For example, if you plan to use the <a
href="http://svn.apache.org/repos/asf/shindig/trunk/features/src/main/javascript/features/tabs/feature.xml";>tabs/feature.xml</a>,
@@ -234,9 +247,9 @@ your gadget will look like the following
<p>You could test your code using the Gadget testing container at:
<a
href="http://localhost:8080/samplecontainer/examples/commoncontainer/index.html";>http://localhost:8080/samplecontainer/examples/commoncontainer/index.html</a>.</p>
<p><img alt="Common Container" src="images/common_container.png"></p>
-<h2 id="create-your-own-feature">Create Your Own Feature</h2>
+<h2 id="create-your-own-feature">Create Your Own Feature<a class="headerlink"
href="#create-your-own-feature" title="Permanent link">¶</a></h2>
<p><span class="label label-important">TODO need to document this</span></p>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources"
title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://code.google.com/p/opensocial-resources/";>The
opensocial-resources project</a></li>
</ul>
Modified: websites/staging/shindig/trunk/content/documentation_java.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_java.html (original)
+++ websites/staging/shindig/trunk/content/documentation_java.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,12 +180,23 @@
</div>
<div class="container">
- <h1 id="documentation-centre-for-java-apache-shindig">Documentation
Centre for Java Apache Shindig</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="documentation-centre-for-java-apache-shindig">Documentation Centre for
Java Apache Shindig<a class="headerlink"
href="#documentation-centre-for-java-apache-shindig" title="Permanent
link">¶</a></h1>
<p>This documentation centre is for developer who wants to work with the Java
version of Apache Shindig.</p>
<ul>
<li><a href="documentation_building_java.html">Building Java Apache
Shindig</a></li>
</ul>
-<h2 id="java-tools">Java Tools</h2>
+<h2 id="java-tools">Java Tools<a class="headerlink" href="#java-tools"
title="Permanent link">¶</a></h2>
<p><a href="http://code.google.com/p/opensocial-java-client/";>OpenSocial
RESTful Java client library</a></p>
<hr>
Modified: websites/staging/shindig/trunk/content/documentation_php.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_php.html (original)
+++ websites/staging/shindig/trunk/content/documentation_php.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="documentation-centre-for-php-apache-shindig">Documentation
Centre for PHP Apache Shindig</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="documentation-centre-for-php-apache-shindig">Documentation Centre for
PHP Apache Shindig<a class="headerlink"
href="#documentation-centre-for-php-apache-shindig" title="Permanent
link">¶</a></h1>
<p><br/>
<span class="alert alert-error">The PHP version of Shindig has been moved to
the attic, this is only kept here for
legacy reasons.</span></p>
@@ -186,7 +199,7 @@ legacy reasons.</span></p>
<ul>
<li><a href="documentation_building_php.html">Building PHP Apache
Shindig</a></li>
</ul>
-<h1 id="php-tools">PHP Tools</h1>
+<h1 id="php-tools">PHP Tools<a class="headerlink" href="#php-tools"
title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://code.google.com/p/opensocial-php-client/";>OpenSocial
RESTful PHP client library</a></li>
<li><a
href="http://www.aitoc.com/en/customization/phpfox_customization.html";>Open
Social Module for phpFox</a></li>
Modified: websites/staging/shindig/trunk/content/documentation_website.html
==============================================================================
--- websites/staging/shindig/trunk/content/documentation_website.html (original)
+++ websites/staging/shindig/trunk/content/documentation_website.html Mon Dec
7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="website-documentation">Website Documentation</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="website-documentation">Website Documentation<a class="headerlink"
href="#website-documentation" title="Permanent link">¶</a></h1>
<p>The Apache Shindig website uses <a
href="http://www.apache.org/dev/cmsref.html";>Apache CMS</a>
to edit, update, and publish content. Apache CMS follows three basic steps
when
updating content on the website:</p>
@@ -195,7 +208,7 @@ However if you prefer to edit the websit
do that as well. The Shindig site uses
<a href="http://daringfireball.net/projects/markdown/";>Markdown</a> to compose
the content of
the site.</p>
-<h2 id="updating-the-website-using-the-bookmarklet">Updating The Website Using
The Bookmarklet</h2>
+<h2 id="updating-the-website-using-the-bookmarklet">Updating The Website Using
The Bookmarklet<a class="headerlink"
href="#updating-the-website-using-the-bookmarklet" title="Permanent
link">¶</a></h2>
<p>The Apache CMS <a
href="http://en.wikipedia.org/wiki/Bookmarklet";>bookmarklet</a> allows you to
edit the Shindig site directly
in your browser. First create a bookmark for the <a
href="https://cms.apache.org/#bookmark";>ASF Bookmarklet</a>. Then navigate
to the <a href="http://shindig.staging.apache.org/";>staging Shindig site</a>
and find the page with the content you want to update.
Modified: websites/staging/shindig/trunk/content/download.html
==============================================================================
--- websites/staging/shindig/trunk/content/download.html (original)
+++ websites/staging/shindig/trunk/content/download.html Mon Dec 7 14:14:54
2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,12 +180,23 @@
</div>
<div class="container">
- <h1 id="apache-shindig-downloads">Apache Shindig Downloads</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apache-shindig-downloads">Apache Shindig Downloads<a
class="headerlink" href="#apache-shindig-downloads" title="Permanent
link">¶</a></h1>
<p>Apache Shindig is distributed under the <a href="license.html"
title="License">Apache License, version 2.0</a>.</p>
<p>Apache Shindig is a distributed as API and as a Web application. You must
have a Servlet container for the Java version installed in order to proceed.
Shindig was successfully tested on Jetty (Java) and Tomcat (Java).</p>
-<h2 id="general-availability-releases">General Availability Releases</h2>
-<h3 id="current-version">Current Version</h3>
+<h2 id="general-availability-releases">General Availability Releases<a
class="headerlink" href="#general-availability-releases" title="Permanent
link">¶</a></h2>
+<h3 id="current-version">Current Version<a class="headerlink"
href="#current-version" title="Permanent link">¶</a></h3>
<p>Apache Shindig 2.5.2 was released the 2014-10-26.</p>
<p><a
href="http://www.apache.org/dist/shindig/2.5.2/";>http://www.apache.org/dist/shindig/2.5.2/</a></p>
<table class="table table-striped">
@@ -233,7 +246,7 @@ Shindig was successfully tested on Jetty
</tbody>
</table>
-<h3 id="previous-releases">Previous Releases</h3>
+<h3 id="previous-releases">Previous Releases<a class="headerlink"
href="#previous-releases" title="Permanent link">¶</a></h3>
<p><a href="http://archive.apache.org/dist/shindig/2.5.1/";>Apache Shindig
2.5.1</a></p>
<p><a href="http://archive.apache.org/dist/shindig/2.5.0-update1/";>Apache
Shindig 2.5.0 Update 1</a></p>
<p><a href="http://archive.apache.org/dist/shindig/2.5.0/";>Apache Shindig
2.5.0</a></p>
@@ -249,19 +262,19 @@ Shindig was successfully tested on Jetty
<p><a href="http://archive.apache.org/dist/shindig/2.0.0/";>Apache Shindig
2.0.0</a></p>
<p><a
href="http://archive.apache.org/dist/shindig/1.1-BETA5-incubating/";>Apache
Shindig 1.1 Beta 5</a></p>
<p><a href="http://archive.apache.org/dist/shindig/1.0.1/";>Apache Shindig
1.0.1</a></p>
-<h2 id="documentation">Documentation</h2>
+<h2 id="documentation">Documentation<a class="headerlink"
href="#documentation" title="Permanent link">¶</a></h2>
<p><span class="label label-important">What do we do about documentation
now?</span></p>
-<h2 id="integration-builds">Integration Builds</h2>
+<h2 id="integration-builds">Integration Builds<a class="headerlink"
href="#integration-builds" title="Permanent link">¶</a></h2>
<p>Apache Shindig uses <a
href="http://shindig.apache.org/integration.html";>Hudson</a> as Continuous
Integration tool. You could download the latest build from the trunk
(i.e. implementation of OpenSocial Spec 2.5) or the branch.</p>
<p><span class="label label-important">What kind of content do we want to put
here?</span></p>
-<h2 id="system-requirements">System Requirements</h2>
+<h2 id="system-requirements">System Requirements<a class="headerlink"
href="#system-requirements" title="Permanent link">¶</a></h2>
<p><span class="label label-important">Verify these requirements are still
correct.</span></p>
<ul>
<li><strong>Java version:</strong> Servlet container supporting Web
Application 2.3 or above and JDK 1.6 or above (as up Shindig 2.5.0 Beta6)</li>
<li><strong>PHP version:</strong> Apache Web Server with mod_rewrite enabled
and PHP 5.2.x with the json, simplexml, mcrypt and curl extensions enabled.</li>
</ul>
-<h2 id="installation-instructions">Installation Instructions</h2>
+<h2 id="installation-instructions">Installation Instructions<a
class="headerlink" href="#installation-instructions" title="Permanent
link">¶</a></h2>
<p><strong>Note:</strong> Read the README files inside the distributions for
detailed instructions.</p>
<ol>
<li>Unzip the distribution archive to the directory you wish to install Apache
Shindig.</li>
Modified: websites/staging/shindig/trunk/content/faq.html
==============================================================================
--- websites/staging/shindig/trunk/content/faq.html (original)
+++ websites/staging/shindig/trunk/content/faq.html Mon Dec 7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="frequently-asked-questions">Frequently Asked Questions<a
class="headerlink" href="#frequently-asked-questions" title="Permanent
link">¶</a></h1>
<hr>
<footer>
Modified: websites/staging/shindig/trunk/content/getting-help.html
==============================================================================
--- websites/staging/shindig/trunk/content/getting-help.html (original)
+++ websites/staging/shindig/trunk/content/getting-help.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,20 +180,31 @@
</div>
<div class="container">
- <h1 id="getting-help">Getting Help</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="getting-help">Getting Help<a class="headerlink" href="#getting-help"
title="Permanent link">¶</a></h1>
<p>So something didn't work as you expected it to? You think that Apache
Shindig is broken.
What should you do?</p>
<p>Here's a list of actions that you can take:</p>
-<h2 id="search-the-mailing-list-archives">Search the mailing list archives</h2>
+<h2 id="search-the-mailing-list-archives">Search the mailing list archives<a
class="headerlink" href="#search-the-mailing-list-archives" title="Permanent
link">¶</a></h2>
<p>Someone else might have experienced the same problem as you before. A list
of
mail-archives can be found on <a href="mail-lists.html">mailing list index
page</a>. Please
search one of them before going any further.</p>
-<h2 id="ask-on-the-mailing-list">Ask on the mailing list</h2>
+<h2 id="ask-on-the-mailing-list">Ask on the mailing list<a class="headerlink"
href="#ask-on-the-mailing-list" title="Permanent link">¶</a></h2>
<p>Our community is very helpful, just ask it the right way. See the
references section,
at the end of this page, for info on how to do that. Subscribe to the <a
href="mail-lists.html">list</a>
and describe your problem there. Don't expect to get an answer right away.
Sometimes it
takes a couple of days.</p>
-<h2 id="submit-an-issue">Submit an issue</h2>
+<h2 id="submit-an-issue">Submit an issue<a class="headerlink"
href="#submit-an-issue" title="Permanent link">¶</a></h2>
<p>If it turns out that there is indeed something wrong with Apache Shindig,
you should report it
to our issue management system <a href="issue-tracking.html">JIRA</a>.</p>
<p>First of all you need to create an account in JIRA. This is so that we can
communicate with you
Modified: websites/staging/shindig/trunk/content/index.html
==============================================================================
--- websites/staging/shindig/trunk/content/index.html (original)
+++ websites/staging/shindig/trunk/content/index.html Mon Dec 7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,22 @@
</div>
<div class="container">
- <div class="hero-unit">
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has been
retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
+
+<div class="hero-unit">
<h1>Welcome To Apache Shindig!</h1>
<p>
Apache Shindig is an OpenSocial container and helps you to start hosting
OpenSocial apps quickly by providing the code to render gadgets, proxy
requests, and handle REST and RPC requests.
Modified: websites/staging/shindig/trunk/content/issue-tracking.html
==============================================================================
--- websites/staging/shindig/trunk/content/issue-tracking.html (original)
+++ websites/staging/shindig/trunk/content/issue-tracking.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,10 +180,21 @@
</div>
<div class="container">
- <h1 id="issue-tracking">Issue Tracking</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="issue-tracking">Issue Tracking<a class="headerlink"
href="#issue-tracking" title="Permanent link">¶</a></h1>
<p>This project uses <a
href="http://www.atlassian.com/software/jira/overview";>JIRA</a> a J2EE-based,
issue
tracking and project management application.</p>
-<h1 id="issue-tracking_1">Issue Tracking</h1>
+<h1 id="issue-tracking_1">Issue Tracking<a class="headerlink"
href="#issue-tracking_1" title="Permanent link">¶</a></h1>
<p>Issues, bugs, and feature requests should be submitted to the following
issue tracking system for this project.</p>
<pre><a
href="https://issues.apache.org/jira/browse/SHINDIG";>https://issues.apache.org/jira/browse/SHINDIG</a></pre>
<hr>
Modified: websites/staging/shindig/trunk/content/jira_conventions.html
==============================================================================
--- websites/staging/shindig/trunk/content/jira_conventions.html (original)
+++ websites/staging/shindig/trunk/content/jira_conventions.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,9 +180,20 @@
</div>
<div class="container">
- <h1 id="apache-shindig-jira-conventions">Apache Shindig JIRA
Conventions</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apache-shindig-jira-conventions">Apache Shindig JIRA Conventions<a
class="headerlink" href="#apache-shindig-jira-conventions" title="Permanent
link">¶</a></h1>
<p>This document describes how Apache Shindig developers should use JIRA, our
issue tracking.</p>
-<h2 id="when-to-create-a-jira-issue">When To Create a JIRA Issue?</h2>
+<h2 id="when-to-create-a-jira-issue">When To Create a JIRA Issue?<a
class="headerlink" href="#when-to-create-a-jira-issue" title="Permanent
link">¶</a></h2>
<p>This section discusses when to create a JIRA issue versus just committing a
change in SVN.</p>
<ul>
<li>Minor changes, like code reformatting, documentation fixes, etc. that
aren't going to
@@ -189,26 +202,26 @@ impact other users can be committed with
pretty much any change of more than 100 lines, should have a JIRA ticket
associated with it,
or at least an email discussion.</li>
</ul>
-<h2 id="how-to-use-issue-details">How To Use Issue Details?</h2>
+<h2 id="how-to-use-issue-details">How To Use Issue Details?<a
class="headerlink" href="#how-to-use-issue-details" title="Permanent
link">¶</a></h2>
<p>This section presents some conventions about the issue fields.</p>
-<h3 id="priority">Priority</h3>
+<h3 id="priority">Priority<a class="headerlink" href="#priority"
title="Permanent link">¶</a></h3>
<p>Committers has the responsibility to realign priority by editing the
issue.</p>
<p>Reasoning: having a correct release note</p>
-<h3 id="assignee">Assignee</h3>
+<h3 id="assignee">Assignee<a class="headerlink" href="#assignee"
title="Permanent link">¶</a></h3>
<p>Committers could assign an issue to a specific committer if he thinks it is
the right committer.</p>
-<h3 id="components">Component/s</h3>
+<h3 id="components">Component/s<a class="headerlink" href="#components"
title="Permanent link">¶</a></h3>
<p>Committers has the responsibility to specify the correct the component by
editing the issue.</p>
<p>Reasoning: having a correct release note.</p>
-<h3 id="affects-versions">Affects Version/s</h3>
+<h3 id="affects-versions">Affects Version/s<a class="headerlink"
href="#affects-versions" title="Permanent link">¶</a></h3>
<p>By default, the Maven team considers that an issue, which affects a given
version, affects
also precedent versions, i.e. issue which affects Maven 2.0.9 will affect also
2.0,
2.0.1 ... 2.0.9. If it is a regression, the committers should specify the
affected versions.</p>
<p>Reasoning: having a correct release note.</p>
-<h3 id="fix-versions">Fix Version/s</h3>
+<h3 id="fix-versions">Fix Version/s<a class="headerlink" href="#fix-versions"
title="Permanent link">¶</a></h3>
<p><span class="label label-important">TO BE DISCUSSED</span></p>
-<h3 id="time-tracking">Time Tracking</h3>
+<h3 id="time-tracking">Time Tracking<a class="headerlink"
href="#time-tracking" title="Permanent link">¶</a></h3>
<p>The Apache Shindig team never uses it. Committers could do it, but like
said, it will never be used.</p>
-<h3 id="further-links">Further Links</h3>
+<h3 id="further-links">Further Links<a class="headerlink"
href="#further-links" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.atlassian.com/software/jira/docs/latest/";>JIRA
Documentation</a></li>
<li><a
href="http://www.atlassian.com/software/jira/docs/latest/issues.html";>What is
an Issue?</a></li>
Modified: websites/staging/shindig/trunk/content/license.html
==============================================================================
--- websites/staging/shindig/trunk/content/license.html (original)
+++ websites/staging/shindig/trunk/content/license.html Mon Dec 7 14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,9 +180,20 @@
</div>
<div class="container">
- <h1 id="project-license">Project License</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="project-license">Project License<a class="headerlink"
href="#project-license" title="Permanent link">¶</a></h1>
<p>Typically the licenses listed for the project are that of the project
itself, and not of dependencies.</p>
-<h2 id="the-apache-software-license-version-20">The Apache Software License,
Version 2.0</h2>
+<h2 id="the-apache-software-license-version-20">The Apache Software License,
Version 2.0<a class="headerlink" href="#the-apache-software-license-version-20"
title="Permanent link">¶</a></h2>
<div class="codehilite"><pre> <span
class="n">Apache</span> <span class="n">License</span>
<span class="n">Version</span> 2<span
class="p">.</span>0<span class="p">,</span> <span class="n">January</span> 2004
<span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">www</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">licenses</span><span class="o">/</span>
Modified: websites/staging/shindig/trunk/content/mail-lists.html
==============================================================================
--- websites/staging/shindig/trunk/content/mail-lists.html (original)
+++ websites/staging/shindig/trunk/content/mail-lists.html Mon Dec 7 14:14:54
2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="project-mailing-lists">Project Mailing Lists</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="project-mailing-lists">Project Mailing Lists<a class="headerlink"
href="#project-mailing-lists" title="Permanent link">¶</a></h1>
<p>These are the mailing lists that have been established for this project.
For each list, there is a subscribe, unsubscribe, and an archive link.</p>
<table class="table table-striped">
Modified: websites/staging/shindig/trunk/content/powered-by.html
==============================================================================
--- websites/staging/shindig/trunk/content/powered-by.html (original)
+++ websites/staging/shindig/trunk/content/powered-by.html Mon Dec 7 14:14:54
2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,15 +180,26 @@
</div>
<div class="container">
- <h1 id="powered-by-apache-shindig">Powered by Apache Shindig</h1>
-<h2 id="software-that-uses-apache-shindig">Software that uses Apache
Shindig</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="powered-by-apache-shindig">Powered by Apache Shindig<a
class="headerlink" href="#powered-by-apache-shindig" title="Permanent
link">¶</a></h1>
+<h2 id="software-that-uses-apache-shindig">Software that uses Apache Shindig<a
class="headerlink" href="#software-that-uses-apache-shindig" title="Permanent
link">¶</a></h2>
<ul>
<li><a href="https://sites.google.com/a/lrlab.to/opensocial-pages/";>OpenSocial
Pages</a></li>
<li><a href="http://www.eurekastreams.org/";>Eureka Streams</a></li>
<li><a href="http://code.google.com/p/partuza/";>Partuza</a></li>
<li><strong>Add more, see <a href="community_overview.html">How to
Contribute</a> page</strong></li>
</ul>
-<h2 id="opensocial-sites-or-projects-using-apache-shindig">Opensocial sites or
projects using Apache Shindig</h2>
+<h2 id="opensocial-sites-or-projects-using-apache-shindig">Opensocial sites or
projects using Apache Shindig<a class="headerlink"
href="#opensocial-sites-or-projects-using-apache-shindig" title="Permanent
link">¶</a></h2>
<ul>
<li><a href="http://rave.apache.org/";>Apache Rave</a></li>
<li><a href="http://www.linkedin.com/";>LinkedIn</a></li>
Modified: websites/staging/shindig/trunk/content/releasing.html
==============================================================================
--- websites/staging/shindig/trunk/content/releasing.html (original)
+++ websites/staging/shindig/trunk/content/releasing.html Mon Dec 7 14:14:54
2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,7 +180,18 @@
</div>
<div class="container">
- <h1 id="apache-shindig-release-process">Apache Shindig Release
Process</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apache-shindig-release-process">Apache Shindig Release Process<a
class="headerlink" href="#apache-shindig-release-process" title="Permanent
link">¶</a></h1>
<p>This document describes how Apache Shindig's committers will make a
release.</p>
<ol>
<li>Release Discussions</li>
@@ -201,11 +214,11 @@ connection.</li>
<li>Some of the build steps require more than the default amount of maven
memory.
You should set MAVEN_OPTS to a larger value, -Xmx512m seems to be
sufficient.</li>
</ol>
-<h2 id="1-release-discussions">1. Release Discussions</h2>
+<h2 id="1-release-discussions">1. Release Discussions<a class="headerlink"
href="#1-release-discussions" title="Permanent link">¶</a></h2>
<p>The starting point will be a consensus in the developer community about the
release and the
JIRA issues to include (or not) in the next release. Typically, the discussion
will be
on the <a href="mail-lists.html">Dev List</a>.</p>
-<h2 id="2-prepare-the-release">2. Prepare The Release</h2>
+<h2 id="2-prepare-the-release">2. Prepare The Release<a class="headerlink"
href="#2-prepare-the-release" title="Permanent link">¶</a></h2>
<p>Duration: 20 min</p>
<p>Now that everybody in the community is happy to push a release, the release
manager needs to
verify the source code before to continue:</p>
@@ -239,7 +252,7 @@ behalf. Verify the SVN logs in the <a hr
mvn release:prepare -Papache-release -Dusername=username -Dpassword=password
</pre></li>
</ol>
-<h2 id="3-stage-the-release">3. Stage The Release</h2>
+<h2 id="3-stage-the-release">3. Stage The Release<a class="headerlink"
href="#3-stage-the-release" title="Permanent link">¶</a></h2>
<p>Duration: 30 min</p>
<p>Call Maven to publish the generated artifacts:</p>
<pre>
@@ -255,7 +268,7 @@ wget -r -H -t1 -nd -N -np -erobots=off
<p>Close the staging repository as described in the points 5 and 6 of the
<a href="http://maven.apache.org/developers/release/index.html";>Maven Release
Process</a>.</p>
-<h2 id="4-deploy-the-documentation">4. Deploy The Documentation</h2>
+<h2 id="4-deploy-the-documentation">4. Deploy The Documentation<a
class="headerlink" href="#4-deploy-the-documentation" title="Permanent
link">¶</a></h2>
<p>Duration: 20 min</p>
<p>Call Maven to publish the generated technical site:</p>
<pre>
@@ -265,7 +278,7 @@ mvn site:deploy
</pre>
<p>Optional: <a href="documentation_website.html">Update</a> the current
website.</p>
-<h2 id="5-propose-a-vote">5. Propose A Vote</h2>
+<h2 id="5-propose-a-vote">5. Propose A Vote<a class="headerlink"
href="#5-propose-a-vote" title="Permanent link">¶</a></h2>
<p>Start a release vote on the <a href="mail-lists.html">Dev List</a>. The
vote must be aligned with
the <a href="http://www.apache.org/foundation/voting.html";>Apache</a> vote
process.</p>
<p>Typically, the mail should include the
@@ -296,13 +309,13 @@ Vote open for 72 hours.
[ ] -1
</pre>
-<h2 id="6-publish-the-release">6. Publish The Release</h2>
+<h2 id="6-publish-the-release">6. Publish The Release<a class="headerlink"
href="#6-publish-the-release" title="Permanent link">¶</a></h2>
<p>Promote the release as described in the points 10 of the
<a href="http://maven.apache.org/developers/release/releasing.html";>Maven
Release Process</a>.</p>
<p>Also, update Jira to specify the release date.</p>
-<h2 id="publish-the-website">Publish The Website</h2>
+<h2 id="publish-the-website">Publish The Website<a class="headerlink"
href="#publish-the-website" title="Permanent link">¶</a></h2>
<p><a href="documentation_website.html">Update</a> the <a
href="download.html">download page</a>.</p>
-<h2 id="8-announce-the-release">8. Announce The Release</h2>
+<h2 id="8-announce-the-release">8. Announce The Release<a class="headerlink"
href="#8-announce-the-release" title="Permanent link">¶</a></h2>
<p>Create an announcement similar to:</p>
<pre>
From: [email protected]
@@ -323,20 +336,20 @@ Enjoy,
-The Apache Shindig Team
</pre>
-<h2 id="9-celebrate-o">9. Celebrate :o)</h2>
-<h2 id="10-notes">10. Notes</h2>
-<h3 id="maven-configuration">Maven Configuration</h3>
+<h2 id="9-celebrate-o">9. Celebrate :o)<a class="headerlink"
href="#9-celebrate-o" title="Permanent link">¶</a></h2>
+<h2 id="10-notes">10. Notes<a class="headerlink" href="#10-notes"
title="Permanent link">¶</a></h2>
+<h3 id="maven-configuration">Maven Configuration<a class="headerlink"
href="#maven-configuration" title="Permanent link">¶</a></h3>
<p>In order to publish the release artifacts to the Apache Maven servers you
need to configure your Maven settings so Maven
knows your Apache credentials. Follow the documentation <a
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>here</a>
to configure Maven correctly.</p>
-<h3 id="php-prerequisites">PHP Prerequisites</h3>
+<h3 id="php-prerequisites">PHP Prerequisites<a class="headerlink"
href="#php-prerequisites" title="Permanent link">¶</a></h3>
<p><span class="alert alert-error">The PHP version of Shindig has been moved
to the attic, this is only kept here for
legacy reasons.</span>
If you are a Java developer who is building a Shindig release chances are you
do not have the necessary PHP
dependencies installed on your machine. You will need to install and
configure PHPUnit and mcrypt (as well as PHP)
in order to run the PHP portion of the Shindig build. The links below are
useful
for Mac users, please add links for other OSes as people build on those
platforms.</p>
-<h4 id="mac">Mac</h4>
+<h4 id="mac">Mac<a class="headerlink" href="#mac" title="Permanent
link">¶</a></h4>
<ul>
<li><a
href="http://www.newmediacampaigns.com/page/install-pear-phpunit-xdebug-on-macosx-snow-leopard";>Installing
PHPUnit</a></li>
<li><a
href="http://www.coolestguyplanettech.com/how-to-install-mcrypt-for-php-on-mac-osx-lion-10-7-development-server/";>Installing
mcrypt</a></li>
Modified: websites/staging/shindig/trunk/content/resources.html
==============================================================================
--- websites/staging/shindig/trunk/content/resources.html (original)
+++ websites/staging/shindig/trunk/content/resources.html Mon Dec 7 14:14:54
2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,13 +180,24 @@
</div>
<div class="container">
- <h1 id="articles-on-apache-shindig">Articles on Apache Shindig</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="articles-on-apache-shindig">Articles on Apache Shindig<a
class="headerlink" href="#articles-on-apache-shindig" title="Permanent
link">¶</a></h1>
<p>All articles on Apache Shindig are listed on our
<a
href="http://cwiki.apache.org/confluence/display/SHINDIG/Index#Index-ArticlesonShindig";>Wiki</a>.</p>
<p>If you are writing an article on Apache Shindig we suggest contacting the
developers on the
mailing list as we would be happy to provide feedback to help ensure accuracy
in your article.
Just ping us on the <a href="mail-lists.html">dev mailing list</a> to get in
touch.</p>
-<h1 id="resources">Resources</h1>
+<h1 id="resources">Resources<a class="headerlink" href="#resources"
title="Permanent link">¶</a></h1>
<p>The following list is some pointers on related OpenSocial resources.</p>
<ul>
<li><a href="http://opensocial.org/";>OpenSocial Foundation</a></li>
Modified: websites/staging/shindig/trunk/content/security.html
==============================================================================
--- websites/staging/shindig/trunk/content/security.html (original)
+++ websites/staging/shindig/trunk/content/security.html Mon Dec 7 14:14:54
2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,13 +180,24 @@
</div>
<div class="container">
- <h1 id="shindig-security-issues">Shindig Security Issues</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="shindig-security-issues">Shindig Security Issues<a class="headerlink"
href="#shindig-security-issues" title="Permanent link">¶</a></h1>
<p>Please note that, except in rare circumstances, binary patches are not
produced for individual vulnerabilities. To obtain the binary fix for a
particular
vulnerability you should upgrade to an Apache Shindig version where that
vulnerability has been fixed.</p>
<p>Source patches, usually in the form of references to SVN commits, may be
provided in either in a vulnerability announcement and/or the vulnerability
details listed on these pages. These source patches may be used by users
wishing to build their own local version of Shindig with just that security
patch rather than upgrade.</p>
-<h3 id="shindig-250-vulnerabilities">Shindig 2.5.0 Vulnerabilities</h3>
+<h3 id="shindig-250-vulnerabilities">Shindig 2.5.0 Vulnerabilities<a
class="headerlink" href="#shindig-250-vulnerabilities" title="Permanent
link">¶</a></h3>
<p><b>Information disclosure <a
href="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2013-4295";>CVE-2013-4295</a></b></p>
<p>The gadget renderer in the PHP version of Apache Shindig
is subject to an XML External Entity (XXE) Injection attack. The
Modified: websites/staging/shindig/trunk/content/source-repository.html
==============================================================================
--- websites/staging/shindig/trunk/content/source-repository.html (original)
+++ websites/staging/shindig/trunk/content/source-repository.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,19 +180,30 @@
</div>
<div class="container">
- <h1 id="source-repository">Source Repository</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="source-repository">Source Repository<a class="headerlink"
href="#source-repository" title="Permanent link">¶</a></h1>
<p>Apache Shindig projects use <a
href="http://subversion.tigris.org/";>Subversion</a> to manage their source
code.
Instructions on Subversion use can be found in the online book <a
href="http://svnbook.red-bean.com/";>Version Control with Subversion</a>.</p>
-<h2 id="web-access">Web Access</h2>
+<h2 id="web-access">Web Access<a class="headerlink" href="#web-access"
title="Permanent link">¶</a></h2>
<p>The following list shows the links to the online source repositories for
the various versions of Apache Shindig:</p>
<pre><a
href="https://svn.apache.org/repos/asf/shindig/trunk/";>https://svn.apache.org/repos/asf/shindig/trunk/</a></pre>
-<h2 id="anonymous-access">Anonymous Access</h2>
+<h2 id="anonymous-access">Anonymous Access<a class="headerlink"
href="#anonymous-access" title="Permanent link">¶</a></h2>
<p>The source can be checked out anonymously from SVN with one of these
commands depending on the development
line you are looking for:</p>
<pre>$ svn checkout http://svn.apache.org/repos/asf/shindig/trunk/
shindig</pre>
-<h2 id="developer-access">Developer Access</h2>
+<h2 id="developer-access">Developer Access<a class="headerlink"
href="#developer-access" title="Permanent link">¶</a></h2>
<p>Everyone can access the Subversion repository via HTTP, but committers must
checkout the Subversion repository
via HTTPS to gain write access:</p>
<pre>$ svn checkout https://svn.apache.org/repos/asf/shindig/trunk/
shindig</pre>
@@ -199,12 +212,12 @@ via HTTPS to gain write access:</p>
(svn will prompt you for your password):</p>
<pre>$ svn commit --username your-username -m "A message"</pre>
-<h2 id="access-from-behind-a-firewall">Access from behind a Firewall</h2>
+<h2 id="access-from-behind-a-firewall">Access from behind a Firewall<a
class="headerlink" href="#access-from-behind-a-firewall" title="Permanent
link">¶</a></h2>
<p>For those users who are stuck behind a corporate firewall which is blocking
HTTP access to the
Subversion repository, you can try to access it via the developer
connection:</p>
<pre>$ svn checkout https://svn.apache.org/repos/asf/shindig/trunk/
shindig</pre>
-<h2 id="access-through-a-proxy">Access through a Proxy</h2>
+<h2 id="access-through-a-proxy">Access through a Proxy<a class="headerlink"
href="#access-through-a-proxy" title="Permanent link">¶</a></h2>
<p>The Subversion client can go through a proxy, if you configure it to do so.
First, edit your
servers configuration file to indicate which proxy to use. The file's location
depends on your
operating system. On Linux or Unix it is located in the directory
~/.subversion. On Windows it
Modified: websites/staging/shindig/trunk/content/svn_conventions.html
==============================================================================
--- websites/staging/shindig/trunk/content/svn_conventions.html (original)
+++ websites/staging/shindig/trunk/content/svn_conventions.html Mon Dec 7
14:14:54 2015
@@ -66,7 +66,9 @@
</head>
<body>
-
+ <div>
+ <span class="alert alert-error">2015/10/23 - Apache Shindig has
been retired. For more information please explore the <a
href="http://attic.apache.org";>Attic</a>.</span>
+ </div>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
@@ -178,13 +180,24 @@
</div>
<div class="container">
- <h1 id="apache-shindig-svn-conventions">Apache Shindig SVN
Conventions</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apache-shindig-svn-conventions">Apache Shindig SVN Conventions<a
class="headerlink" href="#apache-shindig-svn-conventions" title="Permanent
link">¶</a></h1>
<p>This document describes how developers should use SVN, our SCM.</p>
-<h2 id="subversion-configuration">Subversion Configuration</h2>
+<h2 id="subversion-configuration">Subversion Configuration<a
class="headerlink" href="#subversion-configuration" title="Permanent
link">¶</a></h2>
<p>Before committing files in subversion repository, you need to read the
<a href="http://www.apache.org/dev/version-control.html#https-svn";>Committer
Subversion Access</a> document
and you must set your svn client with this properties file: svn-props</p>
-<h2 id="commit-message-template">Commit Message Template</h2>
+<h2 id="commit-message-template">Commit Message Template<a class="headerlink"
href="#commit-message-template" title="Permanent link">¶</a></h2>
<p>Based on <a
href="http://www.apache.org/dev/committers.html#applying-patches";>ASF
committer's FAQ</a>,
the commits should have a message that follows this template:</p>
<pre>
@@ -201,15 +214,15 @@ encouraged to create one for significant
<li><b>Submitted by</b> only needs to be specified when a patch is being
applied for a non-committer.</li>
<li><b>comments</b> some words about the commits.</li>
</ul>
-<h2 id="apply-user-patch">Apply User Patch</h2>
+<h2 id="apply-user-patch">Apply User Patch<a class="headerlink"
href="#apply-user-patch" title="Permanent link">¶</a></h2>
<p>By default, the committer should apply the patch without any <b>major</b>
modifications.
In a second step, the committer could apply any changes as usual.</p>
-<h2 id="edit-commit-message">Edit Commit Message</h2>
+<h2 id="edit-commit-message">Edit Commit Message<a class="headerlink"
href="#edit-commit-message" title="Permanent link">¶</a></h2>
<p>If you want to edit a commit message, you could call:</p>
<pre>svn pe svn:log --revprop -r XXX</pre>
<p>where <b>XXX</b> is the wanted version</p>
-<h2 id="other-useful-subversion-commands-while-developing">Other useful
Subversion commands while developing</h2>
+<h2 id="other-useful-subversion-commands-while-developing">Other useful
Subversion commands while developing<a class="headerlink"
href="#other-useful-subversion-commands-while-developing" title="Permanent
link">¶</a></h2>
<p>If you've done a chunk of work and you would like ditch your changes and
start from
scratch use this command to revert to the original checkout:</p>
<pre>$ svn revert -R</pre>
