Author: buildbot
Date: Sun Feb 7 21:02:46 2016
New Revision: 979780
Log:
Staging update by buildbot for rave
Modified:
websites/staging/rave/trunk/content/ (props changed)
websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html
websites/staging/rave/trunk/content/docs/governance/voting.html
websites/staging/rave/trunk/content/docs/practices/branching.html
websites/staging/rave/trunk/content/documentation/add-page-template.html
websites/staging/rave/trunk/content/documentation/admin-interface-preferences.html
websites/staging/rave/trunk/content/documentation/admin-interface-users.html
websites/staging/rave/trunk/content/documentation/admin-interface-widgets.html
websites/staging/rave/trunk/content/documentation/admin-interface.html
websites/staging/rave/trunk/content/documentation/application-containers.html
websites/staging/rave/trunk/content/documentation/captcha-enabling.html
websites/staging/rave/trunk/content/documentation/components.html
websites/staging/rave/trunk/content/documentation/configure-database.html
websites/staging/rave/trunk/content/documentation/configure-locked-domain.html
websites/staging/rave/trunk/content/documentation/configure-ssl.html
websites/staging/rave/trunk/content/documentation/custom-app-context.html
websites/staging/rave/trunk/content/documentation/custom-gui.html
websites/staging/rave/trunk/content/documentation/custom-widget-renderer.html
websites/staging/rave/trunk/content/documentation/customizing.html
websites/staging/rave/trunk/content/documentation/host-configuration.html
websites/staging/rave/trunk/content/documentation/index.html
websites/staging/rave/trunk/content/documentation/installing.html
websites/staging/rave/trunk/content/documentation/ldap-authentication.html
websites/staging/rave/trunk/content/documentation/manage-static-resources.html
websites/staging/rave/trunk/content/documentation/model-permission-override.html
websites/staging/rave/trunk/content/documentation/mongo-db.html
websites/staging/rave/trunk/content/documentation/new-model-permission-impl.html
websites/staging/rave/trunk/content/documentation/oauth-consumer.html
websites/staging/rave/trunk/content/documentation/omdl-import-export.html
websites/staging/rave/trunk/content/documentation/rave-extensions.html
websites/staging/rave/trunk/content/documentation/script-manager.html
websites/staging/rave/trunk/content/documentation/security-model-permission.html
websites/staging/rave/trunk/content/documentation/sso-login.html
websites/staging/rave/trunk/content/documentation/translate-portal.html
websites/staging/rave/trunk/content/downloads.html
websites/staging/rave/trunk/content/edit-website.html
websites/staging/rave/trunk/content/events/2011/apachecon2011-meetup.html
websites/staging/rave/trunk/content/events/2013/apachecon_na.html
websites/staging/rave/trunk/content/get-involved.html
websites/staging/rave/trunk/content/ide-settings-and-debugging.html
websites/staging/rave/trunk/content/index.html
websites/staging/rave/trunk/content/integration-tests.html
websites/staging/rave/trunk/content/issue-management.html
websites/staging/rave/trunk/content/license.html
websites/staging/rave/trunk/content/mailing-lists.html
websites/staging/rave/trunk/content/people.html
websites/staging/rave/trunk/content/release-management.html
websites/staging/rave/trunk/content/release-process.html
websites/staging/rave/trunk/content/release-setup.html
websites/staging/rave/trunk/content/source.html
Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Feb 7 21:02:46 2016
@@ -1 +1 @@
-1700531
+1729035
Modified:
websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
==============================================================================
--- websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
(original)
+++ websites/staging/rave/trunk/content/docs/governance/consensusBuilding.html
Sun Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,7 +88,18 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>In some cases there is no obvious path to take, or you might be a
new community,
+ <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>
+<p>In some cases there is no obvious path to take, or you might be a new
community,
or a new member of an existing community. In these cases people will often
need to build consensus by making proposals and eliciting responses.</p>
<p>We want to avoid unnecessary discussion and the creation of significant
@@ -95,7 +107,7 @@ amounts of unnecessary mail that everyon
That is not to say that we want to avoid constructive discussion. This is
the lifeblood of a successful project. However, many ASF projects adopt a
shorthand notation for showing support, or otherwise, for a proposal.</p>
-<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)</h2>
+<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)<a
class="headerlink" href="#expressing-support-or-otherwise" title="Permanent
link">¶</a></h2>
<p>The notation used is "+1", "-1" and "0". It's also common to see "+0" and
"-0".</p>
<p>So, what do these notations mean?</p>
<ul>
@@ -112,7 +124,7 @@ to help implement"</li>
like "+1000".</p>
<p>The important thing is that this is not an exact science. It's just a
shorthand
way of communicating strength of feeling.</p>
-<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting</h2>
+<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting<a
class="headerlink" href="#consensus-building-is-not-voting" title="Permanent
link">¶</a></h2>
<p>The confusing thing about this notation is that it is the same notation
used in a formal vote. Knowing when something is a vote and when it is a
preference is important. It's easy to tell though, if the subject does not
have
Modified: websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html
==============================================================================
--- websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html
(original)
+++ websites/staging/rave/trunk/content/docs/governance/lazyConsensus.html Sun
Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,7 +88,18 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>The concept of "Lazy Consensus" is very important in our project.
Lazy
+ <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>
+<p>The concept of "Lazy Consensus" is very important in our project. Lazy
Consensus means that when you are convinced that you know what the community
would like to see happen you can simply assume that you already have consensus
and get on with the work. You don't have to insist people discuss and/or
@@ -98,7 +110,7 @@ You just assume you have the communities
to indicate disapproval. If you believe the community will support your action
you can operate on lazy consensus as long as you are prepared to roll back
any work should a valid objection is raised.</p>
-<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion</h2>
+<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion<a
class="headerlink" href="#avoiding-unnecessary-discussion" title="Permanent
link">¶</a></h2>
<p>The key thing about lazy consensus is that it's easier for people to agree,
by doing nothing, than it is to object, which requires an
alternative to be proposed. This has two effects, firstly people are less
@@ -110,7 +122,7 @@ of the project to watch what is happenin
far down the road will cause upset, but objecting (or asking for clarification
of intent) early is likely to be greeted with relief that someone is watching
and cares.</p>
-<h2 id="stating-lazy-consensus">Stating Lazy Consensus</h2>
+<h2 id="stating-lazy-consensus">Stating Lazy Consensus<a class="headerlink"
href="#stating-lazy-consensus" title="Permanent link">¶</a></h2>
<p>Sometimes a member of the community will believe a specific action is the
correct
one for the community but are not sure enough to proceed with the work under
the
lazy consensus model. In these circumstances they can state Lazy Consensus is
in
@@ -123,7 +135,7 @@ around their proposal, nor are they requ
supports their actions. However, this differs from assuming lazy consensus
since it allows space and time to <a
href="/docs/governance/consensusBuilding.html">express support or
objections</a> and corrections to
the proposal before work begins. </p>
-<h2 id="silence-is-consent">Silence is consent</h2>
+<h2 id="silence-is-consent">Silence is consent<a class="headerlink"
href="#silence-is-consent" title="Permanent link">¶</a></h2>
<p>People may choose to indicate their support for the actions taken with a +1
mail - quick and easy to read and reassuring for the implementer. However,
remember, in a lazy consensus world silence is the equivalent to support. This
Modified: websites/staging/rave/trunk/content/docs/governance/voting.html
==============================================================================
--- websites/staging/rave/trunk/content/docs/governance/voting.html (original)
+++ websites/staging/rave/trunk/content/docs/governance/voting.html Sun Feb 7
21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,21 +88,32 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>Occasionally a "feel" for consensus is not enough. Sometimes we
need to
+ <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>
+<p>Occasionally a "feel" for consensus is not enough. Sometimes we need to
have a measurable consensus. For example, when voting in new committers or
to approve a release. </p>
-<h2 id="preparing-for-a-vote">Preparing for a Vote</h2>
+<h2 id="preparing-for-a-vote">Preparing for a Vote<a class="headerlink"
href="#preparing-for-a-vote" title="Permanent link">¶</a></h2>
<p>Before calling a vote it is important to ensure that the community is given
time to
discuss the upcoming vote. This will be done by posting an email to the list
indicating the intention to call a vote and the options available. By the time
a vote is called there should already be [consensus in the community][4]. The
vote
itself is, normally, a formality.</p>
-<h2 id="calling-a-vote">Calling a Vote</h2>
+<h2 id="calling-a-vote">Calling a Vote<a class="headerlink"
href="#calling-a-vote" title="Permanent link">¶</a></h2>
<p>Once it is time to call the vote a mail is posted with a subject starting
with "{VOTE]". This enables the community members to ensure they do not miss
an important vote thread. It also indicates that this is not consensus building
but a formal vote.</p>
-<h3 id="casting-your-vote">Casting Your Vote</h3>
+<h3 id="casting-your-vote">Casting Your Vote<a class="headerlink"
href="#casting-your-vote" title="Permanent link">¶</a></h3>
<p>The notation used in voting is:</p>
<ul>
<li>+1 Yes I agree </li>
Modified: websites/staging/rave/trunk/content/docs/practices/branching.html
==============================================================================
--- websites/staging/rave/trunk/content/docs/practices/branching.html (original)
+++ websites/staging/rave/trunk/content/docs/practices/branching.html Sun Feb
7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,18 +88,28 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>Typically, development in Rave is done against trunk; however,
occasions arise where significant modifications to the code base are to be made
or there is a desire to keep working on an older version of trunk. In these
instances, a branch should be created to support committing incremental changes
that might leave the codebase in a non-ideal state or provide support for an
older version.<br />
-</p>
+ <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>
+<p>Typically, development in Rave is done against trunk; however, occasions
arise where significant modifications to the code base are to be made or there
is a desire to keep working on an older version of trunk. In these instances,
a branch should be created to support committing incremental changes that might
leave the codebase in a non-ideal state or provide support for an older
version. </p>
<p>This page describes how branches are managed in Rave</p>
-<h4 id="creating-a-new-branch">Creating a new branch</h4>
+<h4 id="creating-a-new-branch">Creating a new branch<a class="headerlink"
href="#creating-a-new-branch" title="Permanent link">¶</a></h4>
<p>Branches should be created sparingly and for valid cause. The committer
proposing the branch should announce their intention to create the branch,
provide a rationale and use <a href="../governance/lazyConsensus.html">lazy
consensus</a> before creating the branch.</p>
<p>The actual task of creating a branch can be accomplished in many ways, one
of which is documented in the <a
href="http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html";>svn book</a></p>
-<h4 id="keeping-the-branch-up-to-date">Keeping the branch up to date</h4>
+<h4 id="keeping-the-branch-up-to-date">Keeping the branch up to date<a
class="headerlink" href="#keeping-the-branch-up-to-date" title="Permanent
link">¶</a></h4>
<p>If the purpose of the branch is to develop large sets of modifications
intended to be integrated into trunk, it is crucial that a working branch
continually merge changes in from trunk. Merging instructions can be found in
the aforementioned svn book.</p>
-<h4 id="integrating-the-branch-into-trunk">Integrating the branch into
trunk</h4>
+<h4 id="integrating-the-branch-into-trunk">Integrating the branch into trunk<a
class="headerlink" href="#integrating-the-branch-into-trunk" title="Permanent
link">¶</a></h4>
<p>Before merging changes from the branch back to trunk, the committer should
seek lazy consensus. The period for this consensus should vary depending on
the nature of the changes and the degree to which they will modify the
codebase. If the committer is unable to determine an appropriate time, 72hrs
can be used to be sure that the entire community has the opportunity to review
the changes.</p>
<p>Branches that are to be merged back into trunk should use the --reintegrate
flag when merging the changes from the branch to trunk. See the svn book for
more details on the operation of merging.</p>
-<h4 id="branch-removal">Branch Removal</h4>
+<h4 id="branch-removal">Branch Removal<a class="headerlink"
href="#branch-removal" title="Permanent link">¶</a></h4>
<p>Removal of a branch should be evaluated on a case-by-case basis. In
general, if a branch was created for the sole purpose of making large code
changes, it is a potential candidate for removal. Again, use the lazy
consensus model to give everyone the opportunity to provide feedback.</p>
</article>
</section>
Modified:
websites/staging/rave/trunk/content/documentation/add-page-template.html
==============================================================================
--- websites/staging/rave/trunk/content/documentation/add-page-template.html
(original)
+++ websites/staging/rave/trunk/content/documentation/add-page-template.html
Sun Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,7 +88,18 @@
</header>
<section id="content" class="row">
<article class="span12">
- <h2 id="adding-a-new-page-layout-for-widgets">Adding a New Page
Layout for Widgets</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>
+<h2 id="adding-a-new-page-layout-for-widgets">Adding a New Page Layout for
Widgets<a class="headerlink" href="#adding-a-new-page-layout-for-widgets"
title="Permanent link">¶</a></h2>
<p>If you want to add a new page layout to Rave on which to render widgets,
here are the steps that currently need to be performed. This is an area that
could be improved in the Rave architecture.</p>
<p>1) Add a new JSP fragment to:</p>
<div class="codehilite"><pre><span class="n">rave</span><span
class="o">-</span><span class="n">portal</span><span class="o">-</span><span
class="n">resources</span> <span class="o">></span> <span
class="n">src</span> <span class="o">></span> <span class="n">main</span>
<span class="o">></span> <span class="n">webapp</span> <span
class="o">></span> <span class="n">WEB</span><span class="o">-</span><span
class="n">INF</span> <span class="o">></span> <span class="n">jsp</span>
<span class="o">></span> <span class="n">layouts</span>
@@ -110,7 +122,7 @@
</li>
</ul>
<p>3) Add a new property to the messages.properties bundle for your layout:</p>
-<div class="codehilite"><pre><span class="n">page</span><span
class="o">.</span><span class="n">general</span><span class="o">.</span><span
class="n">addpage</span><span class="o">.</span><span
class="n">layout</span><span class="o">.<</span><span
class="n">layout</span> <span class="n">code</span><span
class="o">>=<</span><span class="n">Human</span> <span
class="n">Readable</span> <span class="n">Value</span><span
class="o">></span>
+<div class="codehilite"><pre><span class="n">page</span><span
class="p">.</span><span class="n">general</span><span class="p">.</span><span
class="n">addpage</span><span class="p">.</span><span
class="n">layout</span><span class="p">.</span><span class="o"><</span><span
class="n">layout</span> <span class="n">code</span><span
class="o">></span><span class="p">=</span><span class="o"><</span><span
class="n">Human</span> <span class="n">Readable</span> <span
class="n">Value</span><span class="o">></span>
</pre></div>
Modified:
websites/staging/rave/trunk/content/documentation/admin-interface-preferences.html
==============================================================================
---
websites/staging/rave/trunk/content/documentation/admin-interface-preferences.html
(original)
+++
websites/staging/rave/trunk/content/documentation/admin-interface-preferences.html
Sun Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,29 +88,40 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>A portal administrator is able to manage a growing number of
settings that are visible in the portal.</p>
+ <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>
+<p>A portal administrator is able to manage a growing number of settings that
are visible in the portal.</p>
<p>To access the admin interface, see <a href="admin-interface.html">Portal
admin interface</a>.</p>
-<h2 id="page-size">Page Size</h2>
+<h2 id="page-size">Page Size<a class="headerlink" href="#page-size"
title="Permanent link">¶</a></h2>
<p>The number of items from a list per page.
The widget store lists the widgets per 10 items by default.
Changing this value will change the number of Widgets shown per page in the
store.</p>
-<h2 id="title-suffix">Title suffix</h2>
+<h2 id="title-suffix">Title suffix<a class="headerlink" href="#title-suffix"
title="Permanent link">¶</a></h2>
<p>Each page in the portal has a default suffix of "- Rave" in the browser's
title bar.
The administrator can change this into the company name or any other value.</p>
-<h2 id="javascript-debug-mode">JavaScript Debug Mode</h2>
+<h2 id="javascript-debug-mode">JavaScript Debug Mode<a class="headerlink"
href="#javascript-debug-mode" title="Permanent link">¶</a></h2>
<p>Enabled(1): Serves out the individual Rave JavaScript files separately
(rave*.js), unmodified, for easy debugging.<br />
This is the default setting.</p>
<p>Disabled(0): Serves out one single concatenated and minified JavaScript
file (rave_all.min.js) useful for
production environments when performance is more important. This file is
built using the
wro4j-maven-plugin at build time.</p>
-<h2 id="initial-widget-status">Initial Widget Status</h2>
+<h2 id="initial-widget-status">Initial Widget Status<a class="headerlink"
href="#initial-widget-status" title="Permanent link">¶</a></h2>
<p>Defines the status of a Widget that has just been added to the Widget
Store. The default setting is "PREVIEW" which means an administrator must first
publish the Widget before users can add the Widget to their page.</p>
-<h2 id="default-widget-height">Default widget height</h2>
+<h2 id="default-widget-height">Default widget height<a class="headerlink"
href="#default-widget-height" title="Permanent link">¶</a></h2>
<p>The height in pixels that a widget will be rendered with if none is
specified by the widget. Default is 250.</p>
-<h2 id="show-stack-trace-on-error-pages">Show stack trace on error pages</h2>
+<h2 id="show-stack-trace-on-error-pages">Show stack trace on error pages<a
class="headerlink" href="#show-stack-trace-on-error-pages" title="Permanent
link">¶</a></h2>
<p>Enabled(1): Will render a link on the error JSP page to view a stack trace,
useful for debugging purposes.</p>
<p>Disabled(0): Will not render the link or stack trace, useful for production
environments where you don't want to expose code details.</p>
-<h2 id="local-url-of-external-widget-marketplace">Local (URL) of external
widget marketplace</h2>
+<h2 id="local-url-of-external-widget-marketplace">Local (URL) of external
widget marketplace<a class="headerlink"
href="#local-url-of-external-widget-marketplace" title="Permanent
link">¶</a></h2>
<p>Defines the location of a widget marketplace external to the Rave
implementation.</p>
</article>
</section>
Modified:
websites/staging/rave/trunk/content/documentation/admin-interface-users.html
==============================================================================
---
websites/staging/rave/trunk/content/documentation/admin-interface-users.html
(original)
+++
websites/staging/rave/trunk/content/documentation/admin-interface-users.html
Sun Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,18 +88,29 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>A portal administrator is able to manage account data of other
users:</p>
+ <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>
+<p>A portal administrator is able to manage account data of other users:</p>
<ul>
<li>Email address</li>
<li>OpenId URL</li>
</ul>
<p>It is currently not possible to change the username or password of a
user.</p>
<p>To access the admin interface, see <a href="admin-interface.html">Portal
admin interface</a>.</p>
-<h2 id="account-status">Account status</h2>
+<h2 id="account-status">Account status<a class="headerlink"
href="#account-status" title="Permanent link">¶</a></h2>
<p>A User is able to login if his account is <code>enabled</code>, not
<code>expired</code> and not <code>locked</code>. These properties can be
managed
through the admin interface.</p>
<p>Note: an admin cannot disable, expire or lock his own account through the
admin interface</p>
-<h2 id="authorities">Authorities</h2>
+<h2 id="authorities">Authorities<a class="headerlink" href="#authorities"
title="Permanent link">¶</a></h2>
<p>The following authorities are defined for the portal:</p>
<ul>
<li><code>ROLE_USER</code>: a user with this role can view portal pages</li>
Modified:
websites/staging/rave/trunk/content/documentation/admin-interface-widgets.html
==============================================================================
---
websites/staging/rave/trunk/content/documentation/admin-interface-widgets.html
(original)
+++
websites/staging/rave/trunk/content/documentation/admin-interface-widgets.html
Sun Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,12 +88,23 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>Portal admins are able to update the stored metadata of widgets:
URL of the actual widget, its availability in the portal, thumbnail etc.</p>
+ <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>
+<p>Portal admins are able to update the stored metadata of widgets: URL of the
actual widget, its availability in the portal, thumbnail etc.</p>
<p>To access the admin interface, see <a href="admin-interface.html">Portal
admin interface</a>.</p>
-<h2 id="overview">Overview</h2>
+<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h2>
<p>The list of widgets will be growing. In the admin interface it's possible
to filter widgets on status (<code>preview</code>, <code>published</code>),
type (<code>OpenSocial</code>, <code>W3C Widget</code>) or a free text search
in the widget's title and description. All search criteria are optional.</p>
<p>Only widgets that are marked as <code>published</code> will appear in the
portal widget store. If a user adds a new widget, its status is set to
<code>preview</code></p>
-<h2 id="widget-metadata">Widget metadata</h2>
+<h2 id="widget-metadata">Widget metadata<a class="headerlink"
href="#widget-metadata" title="Permanent link">¶</a></h2>
<ul>
<li>Title: the title that is used in the widget store</li>
<li>Location: the URL for the widget definition</li>
Modified: websites/staging/rave/trunk/content/documentation/admin-interface.html
==============================================================================
--- websites/staging/rave/trunk/content/documentation/admin-interface.html
(original)
+++ websites/staging/rave/trunk/content/documentation/admin-interface.html Sun
Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,9 +88,20 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>The Apache Rave Portal has an admin interface to manage data from
<a href="admin-interface-users.html">users</a> and <a
href="admin-interface-widgets.html">widgets</a> (version 0.5-INCUBATING).
+ <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>
+<p>The Apache Rave Portal has an admin interface to manage data from <a
href="admin-interface-users.html">users</a> and <a
href="admin-interface-widgets.html">widgets</a> (version 0.5-INCUBATING).
In the future it may also support manage group data, show portal usage
statistics or change the look and feel of the portal.</p>
-<h2 id="access-the-admin-interface">Access the admin interface</h2>
+<h2 id="access-the-admin-interface">Access the admin interface<a
class="headerlink" href="#access-the-admin-interface" title="Permanent
link">¶</a></h2>
<p>The address of the admin interface is
[http://localhost:8080/portal/app/admin/].<br />
User <code>canonical</code> (password: <code>canonical</code>) is the only
user with admin privileges. Other users will not be able to go to the admin
interface.</p>
</article>
Modified:
websites/staging/rave/trunk/content/documentation/application-containers.html
==============================================================================
---
websites/staging/rave/trunk/content/documentation/application-containers.html
(original)
+++
websites/staging/rave/trunk/content/documentation/application-containers.html
Sun Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,12 +88,23 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>The default distribution of Apache Rave contains Apache Tomcat 6
as application server.
+ <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>
+<p>The default distribution of Apache Rave contains Apache Tomcat 6 as
application server.
For local development the <a
href="http://docs.codehaus.org/display/JETTY/Welcome+files+not+working";>Cargo
Maven 2 plugin</a> is configured to use Tomcat 6. </p>
<p>Apache Rave should work with other application containers as well, but
sometimes extra configuration is necessary. If your application container isn't
mentioned on this page, it only means we have not tested it yet. </p>
-<h2 id="custom-apache-tomcat-6-installation">Custom Apache Tomcat 6
installation</h2>
+<h2 id="custom-apache-tomcat-6-installation">Custom Apache Tomcat 6
installation<a class="headerlink" href="#custom-apache-tomcat-6-installation"
title="Permanent link">¶</a></h2>
<p>To install Apache Rave inside an existing Tomcat 6 instance, make the
following changes:</p>
-<h3 id="increase-memory">Increase memory</h3>
+<h3 id="increase-memory">Increase memory<a class="headerlink"
href="#increase-memory" title="Permanent link">¶</a></h3>
<p>Create <code>bin/setenv.sh</code> with the following contents:</p>
<table class="codehilitetable"><tr><td class="linenos"><div
class="linenodiv"><pre>1
2</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="c">#!/bin/sh</span>
@@ -100,7 +112,7 @@ For local development the <a href="http:
</pre></div>
</td></tr></table>
-<h3 id="add-more-sources-for-the-classpath">Add more sources for the
classpath</h3>
+<h3 id="add-more-sources-for-the-classpath">Add more sources for the
classpath<a class="headerlink" href="#add-more-sources-for-the-classpath"
title="Permanent link">¶</a></h3>
<p>Modify conf/catalina.properties</p>
<div class="codehilite"><pre>common.loader=<span class="cp">${</span><span
class="n">catalina</span><span class="o">.</span><span
class="n">base</span><span class="cp">}</span>/common/classes,<span
class="cp">${</span><span class="n">catalina</span><span
class="o">.</span><span class="n">base</span><span
class="cp">}</span>/common/lib/*.jar,<span class="cp">${</span><span
class="n">catalina</span><span class="o">.</span><span
class="n">base</span><span class="cp">}</span>/lib,<span
class="cp">${</span><span class="n">catalina</span><span
class="o">.</span><span class="n">base</span><span
class="cp">}</span>/lib/*.jar,<span class="cp">${</span><span
class="n">catalina</span><span class="o">.</span><span
class="n">home</span><span class="cp">}</span>/lib,<span
class="cp">${</span><span class="n">catalina</span><span
class="o">.</span><span class="n">home</span><span class="cp">}</span>/lib/*.jar
@@ -108,14 +120,14 @@ shared.loader=<span class="cp">${</span>
</pre></div>
-<h3 id="delete-default-contexts">Delete default contexts</h3>
+<h3 id="delete-default-contexts">Delete default contexts<a class="headerlink"
href="#delete-default-contexts" title="Permanent link">¶</a></h3>
<p>In the webapp folder delete existing <code>ROOT</code> and
<code>docs</code> folders. The OpenSocial container (Shindig) needs the
<code>ROOT</code> context.</p>
-<h3 id="copy-artifacts">Copy artifacts</h3>
+<h3 id="copy-artifacts">Copy artifacts<a class="headerlink"
href="#copy-artifacts" title="Permanent link">¶</a></h3>
<p>Copy the <code>shared/lib</code> folder plus the contents of the
<code>webapp</code> folder to your Tomcat installation. </p>
-<h2 id="apache-tomcat-7">Apache Tomcat 7</h2>
+<h2 id="apache-tomcat-7">Apache Tomcat 7<a class="headerlink"
href="#apache-tomcat-7" title="Permanent link">¶</a></h2>
<p>See the instructions for Tomcat 6.</p>
-<h2 id="jetty-6">Jetty 6</h2>
-<h3 id="wzxhzdk3wzxhzdk4welcome-page-redirect"><a
id="jetty-welcome-page"></a>Welcome page redirect</h3>
+<h2 id="jetty-6">Jetty 6<a class="headerlink" href="#jetty-6" title="Permanent
link">¶</a></h2>
+<h3 id="welcome-page-redirect"><a id="jetty-welcome-page"></a>Welcome page
redirect<a class="headerlink" href="#welcome-page-redirect" title="Permanent
link">¶</a></h3>
<p>Apache Rave works with Jetty 7, but extra configuration is needed to
redirect the user from <code>http://localhost:8080</code> to the login page on
<code>http://localhost:8080/portal/login</code>.
By default Jetty <a href="http://cargo.codehaus.org/Maven2+plugin";>uses the
<code>JspServlet</code></a> for the welcome page, Apache Rave uses
<code>org.springframework.web.servlet.DispatcherServlet</code> from the Spring
Framework. </p>
<p>In order to let Jetty use the DispatcherServlet:</p>
@@ -124,7 +136,7 @@ By default Jetty <a href="http://cargo.c
<li>Go to entry for the servlet org.eclipse.jetty.servlet.DefaultServlet</li>
<li>Change the value of the init parameter <code>welcomeServlets</code> to
<code>true</code>.</li>
</ul>
-<h3 id="root-context-for-apache-shindig">Root context for Apache Shindig</h3>
+<h3 id="root-context-for-apache-shindig">Root context for Apache Shindig<a
class="headerlink" href="#root-context-for-apache-shindig" title="Permanent
link">¶</a></h3>
<p>The OpenSocial container (Apache Shindig) runs under the root context. In
Jetty 6 extra configuration is needed for the root context.</p>
<p>Add a <code>root.xml</code> to the contexts folder which will have a simple
context defined for Shindig with the following entries:</p>
<div class="codehilite"><pre><span class="nt"><Set</span> <span
class="na">name=</span><span class="s">"contextPath"</span><span
class="nt">></span>/<span class="nt"></Set></span>
@@ -132,7 +144,7 @@ By default Jetty <a href="http://cargo.c
</pre></div>
-<h2 id="jetty-7">Jetty 7</h2>
+<h2 id="jetty-7">Jetty 7<a class="headerlink" href="#jetty-7" title="Permanent
link">¶</a></h2>
<p>The <a href="#jetty-welcome-page">Welcome page redirect</a> configuration
is also needed for Jetty 7. Jetty 7 does not need the extra configuration for
the root context.</p>
</article>
</section>
Modified:
websites/staging/rave/trunk/content/documentation/captcha-enabling.html
==============================================================================
--- websites/staging/rave/trunk/content/documentation/captcha-enabling.html
(original)
+++ websites/staging/rave/trunk/content/documentation/captcha-enabling.html Sun
Feb 7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,23 +88,34 @@
</header>
<section id="content" class="row">
<article class="span12">
- <p>Portal administrators can optionally enable CAPTCHA protection on
the new account creation page. The steps for doing this in
+ <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>
+<p>Portal administrators can optionally enable CAPTCHA protection on the new
account creation page. The steps for doing this in
the source release are the following:</p>
-<h2 id="1-get-recaptcha-public-and-private-keys">1) Get reCAPTCHA Public and
Private Keys</h2>
+<h2 id="1-get-recaptcha-public-and-private-keys">1) Get reCAPTCHA Public and
Private Keys<a class="headerlink"
href="#1-get-recaptcha-public-and-private-keys" title="Permanent
link">¶</a></h2>
<p>You must sign up at the <a
href="http://www.google.com/recaptcha/whyrecaptcha";>reCAPTCHA</a> site to
obtain public and private key strings for your host domain. For testing
purpose, you
use <code>localhost</code> as your domain.</p>
-<h2 id="2-add-keys-to-apache-rave">2) Add Keys to Apache Rave</h2>
+<h2 id="2-add-keys-to-apache-rave">2) Add Keys to Apache Rave<a
class="headerlink" href="#2-add-keys-to-apache-rave" title="Permanent
link">¶</a></h2>
<p>Modify the file
<code>rave-portal-resources/src/main/resources/portal.properties</code>.
Change the portal.captcha.* properties to</p>
-<div class="codehilite"><pre> <span class="n">portal</span><span
class="o">.</span><span class="n">captcha</span><span class="o">.</span><span
class="n">enabled</span><span class="o">=</span><span class="n">true</span>
- <span class="n">portal</span><span class="o">.</span><span
class="n">captcha</span><span class="o">.</span><span class="n">key</span><span
class="o">.</span><span class="n">private</span><span class="o">=</span><span
class="n">YOUR_PRIVATE_KEY_STRING</span>
- <span class="n">portal</span><span class="o">.</span><span
class="n">captcha</span><span class="o">.</span><span class="n">key</span><span
class="o">.</span><span class="n">public</span><span class="o">=</span><span
class="n">YOUR_PUBLIC_KEY_STRING</span>
+<div class="codehilite"><pre> <span class="n">portal</span><span
class="p">.</span><span class="n">captcha</span><span class="p">.</span><span
class="n">enabled</span><span class="p">=</span><span class="n">true</span>
+ <span class="n">portal</span><span class="p">.</span><span
class="n">captcha</span><span class="p">.</span><span class="n">key</span><span
class="p">.</span><span class="n">private</span><span class="p">=</span><span
class="n">YOUR_PRIVATE_KEY_STRING</span>
+ <span class="n">portal</span><span class="p">.</span><span
class="n">captcha</span><span class="p">.</span><span class="n">key</span><span
class="p">.</span><span class="n">public</span><span class="p">=</span><span
class="n">YOUR_PUBLIC_KEY_STRING</span>
</pre></div>
<p>When building Apache Rave from source, you should also similarly modify the
test property files
<code>rave-components/rave-core/src/test/resources/portal.properties</code>
and <code>rave-portal/src/test/resources/portal.properties</code> for
proper build testing. </p>
-<h2 id="3-build-and-deploy-apache-rave">3) Build and Deploy Apache Rave</h2>
+<h2 id="3-build-and-deploy-apache-rave">3) Build and Deploy Apache Rave<a
class="headerlink" href="#3-build-and-deploy-apache-rave" title="Permanent
link">¶</a></h2>
<p>Use <code>mvn clean install</code> as usual.</p>
</article>
</section>
Modified: websites/staging/rave/trunk/content/documentation/components.html
==============================================================================
--- websites/staging/rave/trunk/content/documentation/components.html (original)
+++ websites/staging/rave/trunk/content/documentation/components.html Sun Feb
7 21:02:46 2016
@@ -29,6 +29,7 @@
</head>
<body>
+ <div style="background: red"><h1>2016/02/07 - Apache Rave has been retired.
</h1><h2>For more information, please explore the <a
href="http://attic.apache.org/";>Attic</a>. </h2></div>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
@@ -87,28 +88,39 @@
</header>
<section id="content" class="row">
<article class="span12">
- <h2 id="components-in-the-demo-setup">Components in the demo
setup</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>
+<h2 id="components-in-the-demo-setup">Components in the demo setup<a
class="headerlink" href="#components-in-the-demo-setup" title="Permanent
link">¶</a></h2>
<p>The demo setup comes with 4 webapps</p>
-<h3 id="portal">Portal</h3>
+<h3 id="portal">Portal<a class="headerlink" href="#portal" title="Permanent
link">¶</a></h3>
<p>URL: http://localhost:8080/portal</p>
<p>The portal is responsible for rendering and managing pages, user profiles.
Access to the portal is restricted by Spring Security. In the demo setup an
embedded ApacheDS instance is bundled to
demonstrate LDAP authentication.</p>
<p>The portal stores its data in an H2 database through OpenJPA. This database
is shared with Shindig and can be accessed
on http://localhost:11111</p>
-<h3 id="shindig">Shindig</h3>
+<h3 id="shindig">Shindig<a class="headerlink" href="#shindig" title="Permanent
link">¶</a></h3>
<p>URL: http://localhost:8080/ (root context)</p>
<p>Shindig is responsible for rendering OpenSocial gadgets, providing metadata
for OpenSocial gadgets and the social
context of users (group memberships).</p>
-<h3 id="wookie">Wookie</h3>
+<h3 id="wookie">Wookie<a class="headerlink" href="#wookie" title="Permanent
link">¶</a></h3>
<p>URL: http://localhost:8080/wookie</p>
<p>Wookie is responsible for rendering and providing metadata for W3C
Widgets.</p>
<p>Wookie stores its data in a Derby database through OpenJPA.</p>
-<h3 id="demogadgets">Demogadgets</h3>
+<h3 id="demogadgets">Demogadgets<a class="headerlink" href="#demogadgets"
title="Permanent link">¶</a></h3>
<p>URL: http://localhost:8080/demogadgets</p>
<p>This webapp contains (OpenSocial) gadgets that demonstrate what gadgets can
do. The gadget definitions are stored
inside the war file.</p>
-<h2 id="diagram">Diagram</h2>
+<h2 id="diagram">Diagram<a class="headerlink" href="#diagram" title="Permanent
link">¶</a></h2>
<p>If you can't see the image, you can <a
href="../binaries/components_diagram.odg">download its source</a> as OpenOffice
drawing.</p>
<p><img alt="Components diagram" src="../images/components_diagram.png" /></p>
</article>
