incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sc...@apache.org
Subject svn commit: r654328 - in /incubator/public/trunk: site-author/guides/releasing-eclipse-update-site.xml site-publish/guides/releasing-eclipse-update-site.html
Date Wed, 07 May 2008 23:34:54 GMT
Author: schor
Date: Wed May  7 16:34:53 2008
New Revision: 654328

URL: http://svn.apache.org/viewvc?rev=654328&view=rev
Log:
[INCUBATOR-75] add draft of releasing-eclipse-update-site and link to existing releasemanagement
page

Added:
    incubator/public/trunk/site-author/guides/releasing-eclipse-update-site.xml   (with props)
    incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html

Added: incubator/public/trunk/site-author/guides/releasing-eclipse-update-site.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/releasing-eclipse-update-site.xml?rev=654328&view=auto
==============================================================================
--- incubator/public/trunk/site-author/guides/releasing-eclipse-update-site.xml (added)
+++ incubator/public/trunk/site-author/guides/releasing-eclipse-update-site.xml Wed May  7
16:34:53 2008
@@ -0,0 +1,169 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+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
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<document>
+  <properties>
+    <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org
Archives</atom>
+    <title>Apache Incubator: Releasing Eclipse Update Sites (DRAFT)</title>
+  </properties>
+  <body>
+    <section id='intro'><title>A Guide To Releasing Eclipse Update Sites during
Incubation (DRAFT)</title>
+      <section id='TOC'><title>Contents</title><toc/></section>
+      <section id="status">
+        <title>Status - DRAFT</title>
+        <p>
+This document is under active <a href='#help-wanted'>development</a>. This is
a first 
+draft intended to allow public review. 
+        </p>
+      </section>
+      <section id="abstract">
+        <title>Abstract</title>
+        <p> This document is descriptive, not normative. 
+          It aims to guide podlings through the process of 
+          releasing Eclipse update sites with proper mirroring.
+        </p>
+          
+        <p>
+          Podlings may distribute suitable artifacts through an 
+          <a href='http://www.eclipse.org'>Eclipse</a> update site.
+          All artifacts distributed through the update site must satisfy the standard
+          <a href='#distribution-policy-overview'>policy</a>. This implies that:
+          
+          <ul>
+            <li>The update site must be contained within the 
+            <a href='#glossary-podling-dist'>podling distribution directory</a>.</li>
+            <li>All artifacts must be 
+            <a href='http://www.apache.org/dev/release-signing.html#keys-policy'>signed
and summed</a>.</li>
+            <li><a href='#distribution-mirroring'>Mirroring</a> must be
used.</li>
+          </ul>
+         </p>
+ 
+         <p>
+          This guide describes a process for accomplishing this.
+        </p>
+      </section>
+           
+      <section id='setting-up-eclipse-mirroring'><title>Setting up Eclipse mirroring</title>
+        <p>The Eclipse &lt;site> information will contain a URL that Eclipse
uses to get the
+        list of mirrors.  To set this up to use the automatic Apache mirroring system, 
+        make a pair of files in project website space, e.g. in a directory your-project-name/docs/mirrors-support
+          called something like: eclipse-update--xml.cgi and the same name
+          with the type ".html".</p>
+        <p>In the .cgi version, put the following:
+<pre>#!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+#  python includes correctly)
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*</pre>
+        </p>
+        <p>In the .html version, put:
+<pre>&lt;mirrors>
+&lt;mirror url="[preferred]/incubator/your-project-name/eclipse-update-site/"
+label="Recommended mirror: [preferred]"/>
+[if-any http]
+  [for http]
+    &lt;mirror url="[http]/incubator/your-project-name/eclipse-update-site/"
+      label="[http]"/>
+  [end]
+[end]
+[if-any backup]
+  [for backup]
+    &lt;mirror url="[backup]/incubator/your-project-name/eclipse-update-site/"
+      label="Backup mirror: [backup]"/>
+  [end]
+[end]
+&lt;/mirrors></pre>
+        </p>
+        <p>Doing this will return the list of mirrors to Eclipse, as generated by
+        the apache mirroring system</p>
+      </section>
+      <section id='update-site-project'>
+        <title>Creating and maintaining an Eclipse update site project</title>
+        <p>
+          Your project will be making many releases.  Some subset (or perhaps all) of the
+          releases will be available from the update site.  Overtime, the update site itself
+          will be updated to reflect new versions being added.  Plan your release process
to 
+          allow for properly tagging the versions of the update site project that go with
each
+          release.
+        </p>
+        
+        <p>
+          Your project may have several components; these may be on different release cycles.
+          A particular refresh of the update site might involve a subset of the components
+          being managed by the update site.  
+        </p>
+        
+        <p>
+          For those components that are being released, new Jars will be generated, signed,
and added
+          to the update site.  In addition, you will be changing the site.xml file to reflect
+          these newly released components.  The generation process for the update site will
need to
+          combine the newly release components, with the previously released things for previous
+          levels.  If the previous components are small, you can keep these in SVN; if they
are large,
+          consider keeping them in www.apache.org/dist/incubator/your-project/eclipse-update-site
+          since they're there already.
+        </p>
+        
+        <p>The update site project is created with an Eclipse wizard.  You have to
edit the
+        site.xml file.  Here's some tips:
+        <ul>
+          <li>If you are creating an optimized update site (see following section)
include 
+            the pack200="true" attribute on the &lt;site> tag, and set the 
+            digestURL attribute to refer to where in the eventual deployment the digest 
+            will be found.  For instance, set this to something like: 
+            http://www.apache.org/dist/incubator/your-project-name/eclipse-update-site/digest.zip/</li>
+          <li><p>Set the <code>mirrorsURL</code> attribute to the
location on your project's website where
+          the mirroring support cgi script is.  For instance, it might be something like
this:
+          http://incubator.apache.org/your-project-name/mirrors-support/eclipse-update--xml.cgi</p>
+            
+            <p>This is the key to getting the mirroring to work with the Eclipse update
process.</p>
+          </li>
+        </ul></p>        
+      </section>
+      <section id='optimized-sites'>
+        <title>Optimized update sites</title>
+        <p>Starting with Eclipse 3.3, an optimized form of update sites is possible,
through two
+        forms of optimization.  One is making use of the pack200 Jar optimizations, part
of
+        Java 5 and beyond, and the other is having a compact form of the update site information
+        created and placed in a "digest.zip" file.  (Note: don't forget to have your signing

+        process sign this zip.) See the <a href='http://wiki.eclipse.org/Update_Site_Optimization'>
+          Update Site Optimization</a> article for details on creating optimized update
sites.
+        </p>
+      </section>
+      <section id='sample-build-process'>
+        <title>Sample build process</title>
+        <p>A typical build script builds feature Jars from associated Eclipse feature
projects,
+        copies (perhaps from Maven repositories to insure getting a particular release level)
+        jars for the plugins, runs the packer, and builds the digest.  Another script might
+          do signing and signature verification of the jar and zip artifacts.  For a sample
+          of scripts that do this, please refer to the SVN for 
+          <a href='http://svn.apache.org/viewvc/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-05-eclipse-update-site/uimaj-eclipse-update-site/'>
+            the UIMA project's update site</a> - in particular the build.xml and the

+          signEclipseUpdateSite.sh script. 
+        </p>
+      </section> 
+      
+      <section id="help-wanted">
+        <title>Help Wanted!</title>
+        <p>Help to improve the system by posting a patch for this document to the
+           <a href='https://issues.apache.org/jira/browse/INCUBATOR'>incubator section</a>

+           of JIRA or a comment to
+           <a href='lists.html#general+at+incubator.apache.org'>general.AT.incubator.apache.org</a>.
+          </p>
+        </section>
+     
+    </section>
+  </body>
+</document>
+

Propchange: incubator/public/trunk/site-author/guides/releasing-eclipse-update-site.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html?rev=654328&view=auto
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html (added)
+++ incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html Wed May
 7 16:34:53 2008
@@ -0,0 +1,357 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+               "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<html>
+ <head>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <link rel="stylesheet" href="../style/style.css" type="text/css" />
+    <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml"
href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
+    <title>Apache Incubator: Releasing Eclipse Update Sites (DRAFT) - Apache Incubator</title>
+ </head>
+ <body>        
+  <table border="0" width="100%" cellspacing="0">
+   <tr><!-- SITE BANNER AND PROJECT IMAGE -->
+    <td align="left" valign="top">
+<a href="http://www.apache.org/"><img src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" border="0"/></a>
+</td>
+<td align="right">
+<a href="http://incubator.apache.org/"><img src="../images/apache-incubator-logo.png"
alt="Apache Incubator" border="0"/></a>
+</td>
+   </tr>
+  </table>
+  <table border="0" width="100%" cellspacing="4">
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr>
+    <!-- LEFT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navleft">
+           <div class="menuheader"><a 
+href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div>

+    <menu compact="compact">
+          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li>

+          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li>

+          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li>

+            </menu>
+      <div class="menuheader"><a 
+href="/guides/index.html">Entry Guides</a></div> 
+    <menu compact="compact">
+          <li><a href="/guides/proposal.html">Proposal Guide</a></li>

+            </menu>
+      <div class="menuheader"><a 
+href="/guides/index.html">Podling Guides</a></div> 
+    <menu compact="compact">
+          <li><a href="/guides/committer.html">Podling Committers</a></li>

+          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li>

+          <li><a href="/guides/mentor.html">Podling Mentor</a></li>

+          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li>

+          <li><a href="/guides/branding.html">Podling Branding</a></li>

+          <li><a href="/guides/sites.html">Podling Websites</a></li>

+          <li><a href="/guides/graduation.html">Graduation</a></li>

+            </menu>
+      <div class="menuheader"><a 
+href="/ip-clearance/index.html">IP Clearance</a></div> 
+    <menu compact="compact">
+            </menu>
+      <div class="menuheader"><a 
+href="/whoweare.html">Who We Are</a></div> 
+    <menu compact="compact">
+            </menu>
+      <div class="menuheader"><a 
+href="http://www.apache.org">ASF</a></div> 
+    <menu compact="compact">
+          <li><a href="http://www.apache.org/foundation/how-it-works.html">How
Apache Works</a></li> 
+          <li><a href="http://www.apache.org/dev/">Developer Documentation</a></li>

+          <li><a href="http://www.apache.org/foundation/">Foundation</a></li>

+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor
Apache</a></li> 
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>

+            </menu>
+      <div class="menuheader">Other Guides</div>
+    <menu compact="compact">
+          <li><a href="/guides/participation.html">Participation</a></li>

+          <li><a href="/faq.html">General FAQ</a></li> 
+          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li>

+          <li><a href="/guides/lists.html">Mailing Lists</a></li>

+          <li><a href="/guides/website.html">Incubator Website</a></li>

+            </menu>
+      <div class="menuheader"><a 
+href="http://wiki.apache.org/incubator">Wiki</a></div> 
+    <menu compact="compact">
+            </menu>
+
+    <!-- start Ads Server -->
+    <iframe src="http://www.apache.org/ads/buttonbar.html"
+        style="border-width:0; float: left" frameborder="0" scrolling="no"
+        width="135" height="265"></iframe>
+    <!-- end Ads Server -->
+    </td>
+    <!-- CONTENT -->
+    <td align="left" valign="top" class="content">
+                <h2><img src="../images/redarrow.gif" />
+   <a name="intro">A Guide To Releasing Eclipse Update Sites during Incubation (DRAFT)</a>
+</h2>
+<div class="section-content">
+<h3>
+   <a name="TOC">Contents</a>
+</h3>
+<div class="section-content">
+<ul>
+<li><a href='#intro'>
+A Guide To Releasing Eclipse Update Sites during Incubation (DRAFT)
+ </a>
+ <ul>
+<li><a href='#TOC'>
+Contents
+ </a>
+</li>
+<li><a href='#status'>
+Status - DRAFT
+ </a>
+</li>
+<li><a href='#abstract'>
+Abstract
+ </a>
+</li>
+<li><a href='#setting-up-eclipse-mirroring'>
+Setting up Eclipse mirroring
+ </a>
+</li>
+<li><a href='#update-site-project'>
+Creating and maintaining an Eclipse update site project
+ </a>
+</li>
+<li><a href='#optimized-sites'>
+Optimized update sites
+ </a>
+</li>
+<li><a href='#sample-build-process'>
+Sample build process
+ </a>
+</li>
+<li><a href='#help-wanted'>
+Help Wanted!
+ </a>
+</li>
+</ul>
+</li>
+</ul>
+</div>
+<h3>
+   <a name="status">Status - DRAFT</a>
+</h3>
+<div class="section-content">
+<p>
+This document is under active <a href="#help-wanted">development</a>. This is
a first 
+draft intended to allow public review. 
+        </p>
+</div>
+<h3>
+   <a name="abstract">Abstract</a>
+</h3>
+<div class="section-content">
+<p> This document is descriptive, not normative. 
+          It aims to guide podlings through the process of 
+          releasing Eclipse update sites with proper mirroring.
+        </p>
+<p>
+          Podlings may distribute suitable artifacts through an 
+          <a href="http://www.eclipse.org">Eclipse</a> update site.
+          All artifacts distributed through the update site must satisfy the standard
+          <a href="#distribution-policy-overview">policy</a>. This implies that:
+          
+          <ul>
+            <li>The update site must be contained within the 
+            <a href="#glossary-podling-dist">podling distribution directory</a>.</li>
+            <li>All artifacts must be 
+            <a href="http://www.apache.org/dev/release-signing.html#keys-policy">signed
and summed</a>.</li>
+            <li><a href="#distribution-mirroring">Mirroring</a> must be
used.</li>
+          </ul>
+         </p>
+<p>
+          This guide describes a process for accomplishing this.
+        </p>
+</div>
+<h3>
+   <a name="setting-up-eclipse-mirroring">Setting up Eclipse mirroring</a>
+</h3>
+<div class="section-content">
+<p>The Eclipse &lt;site&gt; information will contain a URL that Eclipse uses
to get the
+        list of mirrors.  To set this up to use the automatic Apache mirroring system, 
+        make a pair of files in project website space, e.g. in a directory your-project-name/docs/mirrors-support
+          called something like: eclipse-update--xml.cgi and the same name
+          with the type ".html".</p>
+<p>In the .cgi version, put the following:
+<pre>#!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+#  python includes correctly)
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*</pre>
+        </p>
+<p>In the .html version, put:
+<pre>&lt;mirrors&gt;
+&lt;mirror url="[preferred]/incubator/your-project-name/eclipse-update-site/"
+label="Recommended mirror: [preferred]"/&gt;
+[if-any http]
+  [for http]
+    &lt;mirror url="[http]/incubator/your-project-name/eclipse-update-site/"
+      label="[http]"/&gt;
+  [end]
+[end]
+[if-any backup]
+  [for backup]
+    &lt;mirror url="[backup]/incubator/your-project-name/eclipse-update-site/"
+      label="Backup mirror: [backup]"/&gt;
+  [end]
+[end]
+&lt;/mirrors&gt;</pre>
+        </p>
+<p>Doing this will return the list of mirrors to Eclipse, as generated by
+        the apache mirroring system</p>
+</div>
+<h3>
+   <a name="update-site-project">Creating and maintaining an Eclipse update site project</a>
+</h3>
+<div class="section-content">
+<p>
+          Your project will be making many releases.  Some subset (or perhaps all) of the
+          releases will be available from the update site.  Overtime, the update site itself
+          will be updated to reflect new versions being added.  Plan your release process
to 
+          allow for properly tagging the versions of the update site project that go with
each
+          release.
+        </p>
+<p>
+          Your project may have several components; these may be on different release cycles.
+          A particular refresh of the update site might involve a subset of the components
+          being managed by the update site.  
+        </p>
+<p>
+          For those components that are being released, new Jars will be generated, signed,
and added
+          to the update site.  In addition, you will be changing the site.xml file to reflect
+          these newly released components.  The generation process for the update site will
need to
+          combine the newly release components, with the previously released things for previous
+          levels.  If the previous components are small, you can keep these in SVN; if they
are large,
+          consider keeping them in www.apache.org/dist/incubator/your-project/eclipse-update-site
+          since they're there already.
+        </p>
+<p>The update site project is created with an Eclipse wizard.  You have to edit the
+        site.xml file.  Here's some tips:
+        <ul>
+          <li>If you are creating an optimized update site (see following section)
include 
+            the pack200="true" attribute on the &lt;site&gt; tag, and set the 
+            digestURL attribute to refer to where in the eventual deployment the digest 
+            will be found.  For instance, set this to something like: 
+            http://www.apache.org/dist/incubator/your-project-name/eclipse-update-site/digest.zip/</li>
+          <li><p>Set the <code>mirrorsURL</code> attribute to the
location on your project's website where
+          the mirroring support cgi script is.  For instance, it might be something like
this:
+          http://incubator.apache.org/your-project-name/mirrors-support/eclipse-update--xml.cgi</p>
+            
+            <p>This is the key to getting the mirroring to work with the Eclipse update
process.</p>
+          </li>
+        </ul></p>
+</div>
+<h3>
+   <a name="optimized-sites">Optimized update sites</a>
+</h3>
+<div class="section-content">
+<p>Starting with Eclipse 3.3, an optimized form of update sites is possible, through
two
+        forms of optimization.  One is making use of the pack200 Jar optimizations, part
of
+        Java 5 and beyond, and the other is having a compact form of the update site information
+        created and placed in a "digest.zip" file.  (Note: don't forget to have your signing

+        process sign this zip.) See the <a href="http://wiki.eclipse.org/Update_Site_Optimization">
+          Update Site Optimization</a> article for details on creating optimized update
sites.
+        </p>
+</div>
+<h3>
+   <a name="sample-build-process">Sample build process</a>
+</h3>
+<div class="section-content">
+<p>A typical build script builds feature Jars from associated Eclipse feature projects,
+        copies (perhaps from Maven repositories to insure getting a particular release level)
+        jars for the plugins, runs the packer, and builds the digest.  Another script might
+          do signing and signature verification of the jar and zip artifacts.  For a sample
+          of scripts that do this, please refer to the SVN for 
+          <a href="http://svn.apache.org/viewvc/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-05-eclipse-update-site/uimaj-eclipse-update-site/">
+            the UIMA project's update site</a> - in particular the build.xml and the

+          signEclipseUpdateSite.sh script. 
+        </p>
+</div>
+<h3>
+   <a name="help-wanted">Help Wanted!</a>
+</h3>
+<div class="section-content">
+<p>Help to improve the system by posting a patch for this document to the
+           <a href="https://issues.apache.org/jira/browse/INCUBATOR">incubator section</a>

+           of JIRA or a comment to
+           <a href="lists.html#general+at+incubator.apache.org">general.AT.incubator.apache.org</a>.
+          </p>
+</div>
+</div>
+         </td>
+    <!-- RIGHT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navright">
+           <div class="menuheader"><a 
+href="http://www.apache.org/foundation/sponsorship.html">Thanks</a></div>
+    <menu compact="compact">
+          <li><a href="http://www.apache.org/foundation/thanks.html">Apache sponsors</a></li>

+        </menu>
+      <div class="menuheader"><a 
+href="/projects/index.html">Projects</a></div>
+    <menu compact="compact">
+          <li><a href="/projects/abdera.html">Abdera</a></li> 
+          <li><a href="/projects/buildr.html">Buildr</a></li> 
+          <li><a href="/projects/couchdb.html">CouchDB</a></li> 
+          <li><a href="/projects/jspwiki.html">JSPWiki</a></li> 
+          <li><a href="/projects/imperius.html">Imperius</a></li>

+          <li><a href="/projects/juice.html">JuiCE</a></li> 
+          <li><a href="/projects/lokahi.html">Lokahi</a></li> 
+          <li><a href="/projects/log4php.html">Log4php</a></li> 
+          <li><a href="/projects/lucene.net.html">Lucene.Net</a></li>

+          <li><a href="/projects/nmaven.html">NMaven</a></li> 
+          <li><a href="/projects/pdfbox.html">PDFBox</a></li> 
+          <li><a href="/projects/pig.html">Pig</a></li> 
+          <li><a href="/projects/qpid.html">Qpid</a></li> 
+          <li><a href="/projects/rcf.html">RCF</a></li> 
+          <li><a href="/projects/river.html">River</a></li> 
+          <li><a href="/projects/sanselan.html">Sanselan</a></li>

+          <li><a href="/projects/shindig.html">Shindig</a></li> 
+          <li><a href="/projects/sling.html">Sling</a></li> 
+          <li><a href="/projects/tika.html">Tika</a></li> 
+          <li><a href="/projects/triplesoup.html">TripleSoup</a></li>

+          <li><a href="/projects/tuscany.html">Tuscany</a></li> 
+          <li><a href="/projects/uima.html">UIMA</a></li> 
+          <li><a href="/projects/wsrp4j.html">WSRP4J</a></li> 
+          <li><a href="/projects/xap.html">XAP</a></li> 
+        </menu>
+
+<form action="http://www.google.com/search" method="get">
+    <input value="incubator.apache.org" name="sitesearch" type="hidden"/>
+    <input size="8" name="q" id="query" type="text" value="search..."
+        onclick="if(this.value == 'search...') {this.value = ''}"/>
+    <input name="Search" value="Go" type="submit"/>
+</form>
+    </td>     
+   </tr>
+   <!-- FOOTER -->
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr><td colspan="3" class="footer">
+         Copyright &#169; 2008 The Apache Software Foundation<br />
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License,
Version 2.0</a>.
+       </td>
+   </tr>
+  </table>
+ </body>
+</html>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message