Modified: websites/staging/rave/trunk/content/issue-management.html ============================================================================== --- websites/staging/rave/trunk/content/issue-management.html (original) +++ websites/staging/rave/trunk/content/issue-management.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,8 +88,19 @@ </header> <section id="content" class="row"> <article class="span12"> - <p>All issues are tracked and managed in the Apache JIRA instance (<a href="https://issues.apache.org/jira/browse/rave";>https://issues.apache.org/jira/browse/rave</a>). Please follow the guidelines below when creating issues for Apache Rave in JIRA.</p> -<h4 id="issue-management-guidelines">Issue Management Guidelines</h4> + <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>All issues are tracked and managed in the Apache JIRA instance (<a href="https://issues.apache.org/jira/browse/rave";>https://issues.apache.org/jira/browse/rave</a>). Please follow the guidelines below when creating issues for Apache Rave in JIRA.</p> +<h4 id="issue-management-guidelines">Issue Management Guidelines<a class="headerlink" href="#issue-management-guidelines" title="Permanent link">¶</a></h4> <ul> <li> <p>Use the proper issue type</p> @@ -100,8 +112,7 @@ </li> <li> <p><em>Story</em> </p> -<p>A story represents a single feature that may or may not support an epic. As a rule of thumb, a single developer should be able to complete a story within 1-2 weeks.<br /> -</p> +<p>A story represents a single feature that may or may not support an epic. As a rule of thumb, a single developer should be able to complete a story within 1-2 weeks. </p> </li> <li> <p><em>Sub-task</em></p> @@ -116,13 +127,11 @@ <li> <p>Create links between issues</p> <p>Linking issues is important to provide traceability and overall reduction in management complexity for the issue tracker. Links connect two different issues with a meaningful relationship. You may use any of the available links when connecting two issues together. </p> -<p>NOTE: There is no explicity Epic/Story relationship built into JIRA. If you are creating a story that supports an epic you must relate it via the "is part of" link.<br /> -</p> +<p>NOTE: There is no explicity Epic/Story relationship built into JIRA. If you are creating a story that supports an epic you must relate it via the "is part of" link. </p> </li> <li> <p>Look for similar issues before creating a new one</p> -<p>Often, there is an existing issue that is similar to the one that you are creating. Before creating a new issue, look for a similar one and either update it to reflect additional usages/error conditions.<br /> -</p> +<p>Often, there is an existing issue that is similar to the one that you are creating. Before creating a new issue, look for a similar one and either update it to reflect additional usages/error conditions. </p> </li> <li> <p>Assign the correct component</p>
Modified: websites/staging/rave/trunk/content/license.html ============================================================================== --- websites/staging/rave/trunk/content/license.html (original) +++ websites/staging/rave/trunk/content/license.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>Apache License<br></br>Version 2.0, January 2004<br></br> + <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>Apache License<br></br>Version 2.0, January 2004<br></br> <a href="http://www.apache.org/licenses/";>http://www.apache.org/licenses/</a> </p> <p>TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION</p> <p><strong><a name="definitions">1. Definitions</a></strong>.</p> @@ -241,7 +253,7 @@ harmless for any liability incurred by, Contributor by reason of your accepting any such warranty or additional liability.</p> <p>END OF TERMS AND CONDITIONS</p> -<h1 id="apply">APPENDIX: How to apply the Apache License to your work</h1> +<h1 id="apply">APPENDIX: How to apply the Apache License to your work<a class="headerlink" href="#apply" title="Permanent link">¶</a></h1> <p>To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be @@ -249,19 +261,20 @@ enclosed in the appropriate comment synt recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.</p> -<div class="codehilite"><pre> Copyright [yyyy] [name of copyright owner] +<div class="codehilite"><pre> <span class="p">:::</span><span class="n">text</span> + <span class="n">Copyright</span> <span class="p">[</span><span class="n">yyyy</span><span class="p">]</span> <span class="p">[</span><span class="n">name</span> <span class="n">of</span> <span class="n">copyright</span> <span class="n">owner</span><span class="p">]</span> - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at + <span class="n">Licensed</span> <span class="n">under</span> <span class="n">the</span> <span class="n">Apache</span> <span class="n">License</span><span class="p">,</span> <span class="n">Version</span> 2<span class="p">.</span>0 <span class="p">(</span><span class="n">the</span> "<span class="n">License</span>"<span class="p">);</span> + <span class="n">you</span> <span class="n">may</span> <span class="n">not</span> <span class="n">use</span> <span class="n">this</span> <span class="n">file</span> <span class="n">except</span> <span class="n">in</span> <span class="n">compliance</span> <span class="n">with</span> <span class="n">the</span> <span class="n">License</span><span class="p">.</span> + <span class="n">You</span> <span class="n">may</span> <span class="n">obtain</span> <span class="n">a</span> <span class="n">copy</span> <span class="n">of</span> <span class="n">the</span> <span class="n">License</span> <span class="n">at</span> - http://www.apache.org/licenses/LICENSE-2.0 + <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><span class="n">LICENSE</span><span class="o">-</span>2<span class="p">.</span>0 - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. + <span class="n">Unless</span> <span class="n">required</span> <span class="n">by</span> <span class="n">applicable</span> <span class="n">law</span> <span class="n">or</span> <span class="n">agreed</span> <span class="n">to</span> <span class="n">in</span> <span class="n">writing</span><span class="p">,</span> <span class="n">software</span> + <span class="n">distributed</span> <span class="n">under</span> <span class="n">the</span> <span class="n">License</span> <span class="n">is</span> <span class="n">distributed</span> <span class="n">on</span> <span class="n">an</span> "<span class="n">AS</span> <span class="n">IS</span>" <span class="n">BASIS</span><span class="p">,</span> + <span class="n">WITHOUT</span> <span class="n">WARRANTIES</span> <span class="n">OR</span> <span class="n">CONDITIONS</span> <span class="n">OF</span> <span class="n">ANY</span> <span class="n">KIND</span><span class="p">,</span> <span class="n">either</span> <span class="n">express</span> <span class="n">or</span> <span class="n">implied</span><span class="p">.</span> + <span class="n">See</span> <span class="n">the</span> <span class="n">License</span> <span class="k">for</span> <span class="n">the</span> <span class="n">specific</span> <span class="n">language</span> <span class="n">governing</span> <span class="n">permissions</span> <span class="n">and</span> + <span class="n">limitations</span> <span class="n">under</span> <span class="n">the</span> <span class="n">License</span><span class="p">.</span> </pre></div> </article> </section> Modified: websites/staging/rave/trunk/content/mailing-lists.html ============================================================================== --- websites/staging/rave/trunk/content/mailing-lists.html (original) +++ websites/staging/rave/trunk/content/mailing-lists.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,8 +88,19 @@ </header> <section id="content" class="row"> <article class="span12"> - <p>We welcome you to join our mailing lists and let us know about your thoughts or ideas about Rave.</p> -<h3 id="apache-rave-users-mailing-list">Apache Rave Users Mailing List</h3> + <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>We welcome you to join our mailing lists and let us know about your thoughts or ideas about Rave.</p> +<h3 id="apache-rave-users-mailing-list">Apache Rave Users Mailing List<a class="headerlink" href="#apache-rave-users-mailing-list" title="Permanent link">¶</a></h3> <p>This is where you can ask questions about how to use Apache Rave or how to make a your own portal with Apache Rave. But don't forget to look in the <a href="/documentation/index.html">documentation</a> first, please!</p> <ul> @@ -101,7 +113,7 @@ But don't forget to look in the <a href= </ul> </li> </ul> -<h3 id="apache-rave-developer-mailing-list">Apache Rave Developer Mailing List</h3> +<h3 id="apache-rave-developer-mailing-list">Apache Rave Developer Mailing List<a class="headerlink" href="#apache-rave-developer-mailing-list" title="Permanent link">¶</a></h3> <p>This is where discussions about the development of Apache Rave happens. This list is used to coordinate activities and ensure we are all pulling in the same direction.</p> <ul> @@ -114,7 +126,7 @@ ensure we are all pulling in the same di </ul> </li> </ul> -<h3 id="commits-mailing-list">Commits Mailing List</h3> +<h3 id="commits-mailing-list">Commits Mailing List<a class="headerlink" href="#commits-mailing-list" title="Permanent link">¶</a></h3> <p>This is where the community receives automated notifications of any changes to the Rave code and documentation.</p> <ul> Modified: websites/staging/rave/trunk/content/people.html ============================================================================== --- websites/staging/rave/trunk/content/people.html (original) +++ websites/staging/rave/trunk/content/people.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,10 +88,21 @@ </header> <section id="content" class="row"> <article class="span12"> - <p>Apache Rave is a community developed project. The list below + <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>Apache Rave is a community developed project. The list below is a partial list of contributors to the project, for a complete list you'd have to look at all contributors to our issue tracker, mailing list and version control.</p> -<table> +<table class="table"> <thead> <tr> <th>Apache ID</th> @@ -222,8 +234,8 @@ to look at all contributors to our issue </tr> </tbody> </table> -<h3 id="emeritus-contributors"><a href="http://www.apache.org/foundation/glossary.html#Emeritus";>Emeritus</a> Contributors</h3> -<table> +<h3 id="emeritus-contributors"><a href="http://www.apache.org/foundation/glossary.html#Emeritus";>Emeritus</a> Contributors<a class="headerlink" href="#emeritus-contributors" title="Permanent link">¶</a></h3> +<table class="table"> <thead> <tr> <th>Apache ID</th> Modified: websites/staging/rave/trunk/content/release-management.html ============================================================================== --- websites/staging/rave/trunk/content/release-management.html (original) +++ websites/staging/rave/trunk/content/release-management.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>Release artifacts are distributed via the Apache Nexus repository for both SNAPSHOT and versioned releases. In addition to Nexus, a source and standalone binary release will be made available via the <a href="http://www.apache.org/dist/rave";>Apache Distribution Area</a>. </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>Release artifacts are distributed via the Apache Nexus repository for both SNAPSHOT and versioned releases. In addition to Nexus, a source and standalone binary release will be made available via the <a href="http://www.apache.org/dist/rave";>Apache Distribution Area</a>. </p> <p>To familiarize yourself with the notions and requirements for releasing artifacts, please checkout the Apache Release FAQ.</p> -<h3 id="apache-rave-release-guidelines">Apache Rave Release Guidelines</h3> +<h3 id="apache-rave-release-guidelines">Apache Rave Release Guidelines<a class="headerlink" href="#apache-rave-release-guidelines" title="Permanent link">¶</a></h3> <ul> <li><a href="release-setup.html">Release Manager Configuration Guide</a></li> <li><a href="release-process.html">Release Process</a></li> Modified: websites/staging/rave/trunk/content/release-process.html ============================================================================== --- websites/staging/rave/trunk/content/release-process.html (original) +++ websites/staging/rave/trunk/content/release-process.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,11 +88,22 @@ </header> <section id="content" class="row"> <article class="span12"> - <h3 id="release-steps-overview">Release Steps Overview</h3> + <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> +<h3 id="release-steps-overview">Release Steps Overview<a class="headerlink" href="#release-steps-overview" title="Permanent link">¶</a></h3> <p>There are two distinct sets of artifacts that are released on independent schedules: rave-master & rave-project. The rave-master is the project metadata (committers, roles, etc) and only needs to be released when there is a change in the structure of the project itself (committers, mentors, etc). The rave-project artifacts are comprised of all rave source code, binaries and a standalone demo. </p> <p>All of the steps below apply to both the master and project releases, unless otherwise specified. As an alternative to releasing separately, the projects MAY be released together as one combined release. The steps for this can be found below. (<a href="#combined">Combined Release Steps</a>)</p> <p>Additionally, most of the steps in the release process can be automated using the release scripts found in the <a href="http://svn.apache.org/repos/asf/rave/release-management/";>repository</a>. Steps for the release scripts are found below. (<a href="#scripted">Scripted Release Steps</a>).</p> -<h4 id="common-release-steps">Common Release Steps</h4> +<h4 id="common-release-steps">Common Release Steps<a class="headerlink" href="#common-release-steps" title="Permanent link">¶</a></h4> <ol> <li> <p>Environment setup for releasing artifacts (same for SNAPSHOTs and releases) </p> @@ -324,7 +336,7 @@ </ul> </li> </ol> -<h4 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h4> +<h4 id="recovering-from-a-vetoed-release">Recovering from a vetoed release<a class="headerlink" href="#recovering-from-a-vetoed-release" title="Permanent link">¶</a></h4> <ol> <li> <p>Reply to the initial vote email and prepend to the original subject -</p> @@ -358,7 +370,7 @@ </li> </ol> <p><a name="verify_signatures"></a></p> -<h4 id="verifying-release-signatures">Verifying release signatures</h4> +<h4 id="verifying-release-signatures">Verifying release signatures<a class="headerlink" href="#verifying-release-signatures" title="Permanent link">¶</a></h4> <p>On unix platforms the following command can be executed -</p> <div class="codehilite"><pre> for file in `find . -type f -iname '*.asc'` do @@ -371,7 +383,7 @@ <p>gpg: Good signature from ... gpg: Signature made ...</p> <p><a name="combined"></a></p> -<h4 id="combined-release">Combined Release</h4> +<h4 id="combined-release">Combined Release<a class="headerlink" href="#combined-release" title="Permanent link">¶</a></h4> <p>In order to perform a combined release of the rave-master and rave-project trunks, do the following: </p> <ul> <li>Perform Steps 1-9 of the <a href="#release-steps">release</a> for Rave Master & Rave Project <ul> @@ -386,7 +398,7 @@ gpg: Signature made ...</p> </li> </ul> <p><a name="scripted"></a></p> -<h4 id="scripted-release">Scripted Release</h4> +<h4 id="scripted-release">Scripted Release<a class="headerlink" href="#scripted-release" title="Permanent link">¶</a></h4> <p>There are two scripts in the repository created to facilitate simpler releases: release.sh & publish.sh. The release script handles steps up to the VOTE e-mails and the publish script handles publishing the artifacts to the mirrors once a successful vote has been achieved. </p> <p>To use the scripts, do the following:</p> <ol> Modified: websites/staging/rave/trunk/content/release-setup.html ============================================================================== --- websites/staging/rave/trunk/content/release-setup.html (original) +++ websites/staging/rave/trunk/content/release-setup.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,15 +88,26 @@ </header> <section id="content" class="row"> <article class="span12"> - <p>These setup steps only need to be performed on a particular machine once.</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>These setup steps only need to be performed on a particular machine once.</p> <p><em>Developers using Linux workstations can skip over the references to Cygwin. If using Windows, install cygwin, including Utils/gnupg and Net/openssh packages.</em></p> -<h4 id="create-and-install-a-ssh-key">Create and install a SSH key</h4> +<h4 id="create-and-install-a-ssh-key">Create and install a SSH key<a class="headerlink" href="#create-and-install-a-ssh-key" title="Permanent link">¶</a></h4> <ol> <li>Open a shell window. If using Windows, open a cygwin window.</li> <li>Use ssh-keygen to create an SSH key.</li> </ol> <p><em>Follow the latest steps and guides on the <a href="http://www.apache.org/dev/openpgp.html#generate-key";>ASF website</a> as you should <strong>NOT</strong> be using SHA1 and new keys <strong>MUST</strong> be at least 4096 bits.</em></p> -<div class="codehilite"><pre> <span class="nv">$</span> <span class="nv">ssh</span><span class="o">-</span><span class="n">keygen</span> <span class="o">-</span><span class="n">t</span> <span class="n">rsa</span> <span class="o">-</span><span class="n">b</span> <span class="mi">4096</span> +<div class="codehilite"><pre> $ <span class="n">ssh</span><span class="o">-</span><span class="n">keygen</span> <span class="o">-</span><span class="n">t</span> <span class="n">rsa</span> <span class="o">-</span><span class="n">b</span> 4096 </pre></div> @@ -103,8 +115,7 @@ <p><em>See <a href="http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html";>Authenticating By Public Key (OpenSSH)</a> for a good description on why and how to perform this task.</em></p> <ol> <li> -<p>SCP your SSH public key ~/.ssh/id_dsa.pub created in last step to ~/id_dsa.pub on people.apache.org.<br /> -</p> +<p>SCP your SSH public key ~/.ssh/id_dsa.pub created in last step to ~/id_dsa.pub on people.apache.org. </p> <p>$ cd ~/.ssh<br /> $ scp id_dsa.pub <your userid>@people.apache.org:id_dsa.pub<br /> $ You will be prompted for your password.</p> @@ -112,8 +123,7 @@ <li> <p>Use ssh to login to people.apache.org</p> <p>$ cd ~ <br /> - $ ssh <your userid>@people.apache.org<br /> -</p> + $ ssh <your userid>@people.apache.org </p> </li> </ol> <p>At this point, you will still be prompted for your password.</p> @@ -121,8 +131,7 @@ <li> <p>Create a ~/.ssh folder in your home directory on people.apache.org and change its file mode to 700.</p> <p>$ mkdir ~/.ssh<br /> - $ chmod 700 ~/.ssh<br /> -</p> + $ chmod 700 ~/.ssh </p> </li> <li> <p>Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.</p> @@ -143,7 +152,7 @@ <p><em>If you are still prompted for a password, then you have not set up the ssh keys properly. Review the steps above and ensure that all of the steps were followed properly. Or, maybe the instructions are still not quite right and they still need some adjusting. In that case, please update the instructions accordingly.</em></p> </li> </ol> -<h4 id="create-a-gpg-key">Create a GPG key</h4> +<h4 id="create-a-gpg-key">Create a GPG key<a class="headerlink" href="#create-a-gpg-key" title="Permanent link">¶</a></h4> <ol> <li>Open a shell window. If using Windows, open a cygwin window.</li> <li> @@ -172,7 +181,7 @@ <p>Following the instructions in http://people.apache.org/~henkp/trust/ and ask multiple (at least 3) current Apache committers to sign your public key.</p> </li> </ol> -<h4 id="configure-maven">Configure Maven</h4> +<h4 id="configure-maven">Configure Maven<a class="headerlink" href="#configure-maven" title="Permanent link">¶</a></h4> <ol> <li>Update your ~/.m2/settings.xml with the properties from <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>Publishing Maven Artifacts</a></li> </ol> Modified: websites/staging/rave/trunk/content/source.html ============================================================================== --- websites/staging/rave/trunk/content/source.html (original) +++ websites/staging/rave/trunk/content/source.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>We use <a href="http://subversion.apache.org";>Apache Subversion</a> for version control. You can <a href="http://svn.apache.org/viewvc/rave/";>browse our + <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>We use <a href="http://subversion.apache.org";>Apache Subversion</a> for version control. You can <a href="http://svn.apache.org/viewvc/rave/";>browse our repository</a> in your web browser.</p> -<h2 id="getting-the-source-code">Getting the source code</h2> +<h2 id="getting-the-source-code">Getting the source code<a class="headerlink" href="#getting-the-source-code" title="Permanent link">¶</a></h2> <p>The instructions on this page will help you get started using command line tools. If you prefer to work in an IDE then we have <a href="ide-settings-and-debugging.html">separate instructions</a> for you.</p> -<h3 id="git-access">Git access</h3> +<h3 id="git-access">Git access<a class="headerlink" href="#git-access" title="Permanent link">¶</a></h3> <div class="codehilite"><pre><span class="n">git</span> <span class="n">clone</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</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">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">rave</span> </pre></div> -<h2 id="building-and-running">Building and Running</h2> +<h2 id="building-and-running">Building and Running<a class="headerlink" href="#building-and-running" title="Permanent link">¶</a></h2> <p>To build from source code:</p> -<h3 id="requirements">Requirements:</h3> +<h3 id="requirements">Requirements:<a class="headerlink" href="#requirements" title="Permanent link">¶</a></h3> <ul> <li>Sources compilation require Java SE 6 or higher.</li> <li>The project is built with Apache Maven 3+ (version 3.0.3 or later is <em>required</em>) <a href="http://maven.apache.org/download.html";>Download</a> and <a href="http://maven.apache.org/download.html#Installation";>install</a></li> </ul> -<h3 id="apache-rave-project">Apache Rave Project</h3> +<h3 id="apache-rave-project">Apache Rave Project<a class="headerlink" href="#apache-rave-project" title="Permanent link">¶</a></h3> <p>To build the Apache Rave project invoke maven from the project root directory:</p> <div class="codehilite"><pre><span class="n">mvn</span> <span class="n">install</span> </pre></div> @@ -122,7 +134,7 @@ you have to add these URLs in your proxy </pre></div> -<h3 id="deploying-and-running-on-tomcat">Deploying and Running on Tomcat</h3> +<h3 id="deploying-and-running-on-tomcat">Deploying and Running on Tomcat<a class="headerlink" href="#deploying-and-running-on-tomcat" title="Permanent link">¶</a></h3> <p>To run a local Tomcat instance with rave-shindig and rave-portal and Wookie deployed:</p> <ul> <li> @@ -136,7 +148,7 @@ you have to add these URLs in your proxy <li>open url http://localhost:8080/portal in a browser</li> <li>press Ctrl-C in the console to stop Tomcat again</li> </ul> -<h3 id="logging-in">Logging in</h3> +<h3 id="logging-in">Logging in<a class="headerlink" href="#logging-in" title="Permanent link">¶</a></h3> <p>Once the server is running:</p> <ul> <li>localhost:8080/portal</li> @@ -149,7 +161,7 @@ you have to add these URLs in your proxy </ul> </li> </ul> -<h3 id="apache-rave-master-project">Apache Rave Master Project</h3> +<h3 id="apache-rave-master-project">Apache Rave Master Project<a class="headerlink" href="#apache-rave-master-project" title="Permanent link">¶</a></h3> <p>The Apache Rave project depends on the separate Apache Rave Master project which defines general and global settings for the whole of the Apache Rave project, independent of a specific release. As its rave-master-pom is already published to the Apache Snapshots repository, there is no need to check it out manually and build it locally yourself, unless changes are @@ -164,7 +176,7 @@ needed on general and global level.</p> </pre></div> -<h3 id="running-the-integration-tests">Running the integration tests</h3> +<h3 id="running-the-integration-tests">Running the integration tests<a class="headerlink" href="#running-the-integration-tests" title="Permanent link">¶</a></h3> <p>See the article about <a href="integration-tests.html">integration tests</a></p> </article> </section>
