Author: buildbot
Date: Fri Jan 3 15:04:30 2014
New Revision: 892657
Log:
Staging update by buildbot for juddi
Modified:
websites/staging/juddi/trunk/content/ (props changed)
websites/staging/juddi/trunk/content/committers.html
Propchange: websites/staging/juddi/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 3 15:04:30 2014
@@ -1 +1 @@
-1555102
+1555120
Modified: websites/staging/juddi/trunk/content/committers.html
==============================================================================
--- websites/staging/juddi/trunk/content/committers.html (original)
+++ websites/staging/juddi/trunk/content/committers.html Fri Jan 3 15:04:30
2014
@@ -20,7 +20,7 @@
<html lang="en" dir="LTR">
<head>
<meta charset="utf-8">
- <title>Apache jUDDICommiter Notes
</title>
+ <title>Apache jUDDICommiter Notes</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="jUDDI (pronounced Judy) is an open
source Java implementation of the Universal Description, Discovery, and
Integration (UDDI v3) specification for (Web) Services.">
<meta name="author" content="Apache Software Foundation">
@@ -111,7 +111,7 @@
<div class="row">
<div class="span12" >
<div class="well">
- <h1>Commiter Notes
</h1>
+ <h1>Commiter Notes</h1>
</div>
</div>
</div>
@@ -154,11 +154,24 @@
<div class="span10" >
<h2 id="updating-the-juddi-web-site">Updating the jUDDI Web
Site</h2>
-<p>The site source is located under our source tree at juddi/src/site. To
build the site, simply invoke mvn site in juddi/site. The built sources will be
located at juddi/target/site. You should get a clean build, and no broken
links. There aren't any known issues with the site.</p>
-<p>You must test your builds locally by running mvn site on your local box.
You can do this by invoking 'mvn site' in the juddi root directory.</p>
-<p>The commit process is a bit complicated. The live site is hosted under the
site source tree, -not- the juddi src tree. The juddi/target/site directory
hierarchy maps to the ws-site/targets/juddi directory hierarchy. Once you've
built the site copy the latter hierarchy to the former, and then commit the
changes. The live site is updated about every 6 hours from cvs.</p>
-<p>You must -also- commit the changes you've made under juddi/src/site to
persist the changes for the next committer to be able to reproduce your
modifications.</p>
-<p>To fully clean any site build you've created, you can safely delete
everything under juddi/target.</p>
+<p>The site source is located under our source tree at <a
href="http://svn.apache.org/repos/asf/juddi/cms-site/";>juddi/src/cms-site</a>.
</p>
+<p>There are two ways to edit the content for this site.</p>
+<ol>
+<li>Edit the files in the Subversion repository</li>
+<li>Using <a href="https://cms.apache.org/#bookmark";>Apache's CMS
Bookmarklet</a></li>
+<li>Simple <a
href="https://cms.apache.org/redirect?uri=http://juddi.apache.org/";>Click
here</a></li>
+</ol>
+<p>Once you're done making edits, commit the changes. Changes can be previewed
on the <a href="http://juddi.staging.apache.org/";>staging site</a>. If you're
satisfied with the results, then publish it to the production site.</p>
+<p>Still have questions? Check out <a
href="http://www.apache.org/dev/cms.html";>this</a>, <a
href="http://www.apache.org/dev/cmsref.html";>this</a> and <a
href="http://michelf.ca/projects/php-markdown/extra/";>this</a>.</p>
+<p>When updating javadoc or xref sections, it's easier to just use svn and
commit it that way</p>
+<h3 id="notes">Notes</h3>
+<ul>
+<li>Each page has a 'Title' header except for the home page.</li>
+<li>Content is annotated using <a
href="http://daringfireball.net/projects/markdown/syntax";>Markdown</a></li>
+<li>All pages, except for the home page, using this <a
href="http://svn.apache.org/repos/asf/juddi/cms-site/trunk/templates/skeleton.html";>template</a></li>
+<li>The home page, uses this <a
href="http://svn.apache.org/repos/asf/juddi/cms-site/trunk/templates/skeletonHome.html";>template</a></li>
+<li>When updating the navigation bars (top or left hand side), edit both
templates</li>
+</ul>
<h2 id="release-process">Release Process</h2>
<h3 id="release-manager">Release Manager</h3>
<p>One committer will be elected or hopefully volunteer to assemble the binary
releases and label the source tree.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
