You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by mp...@apache.org on 2001/08/01 20:55:57 UTC
cvs commit: jakarta-turbine-site/xdocs/stylesheets project.xml
mpoeschl 01/08/01 11:55:57
Added: . README.txt build.properties build.xml
xdocs index.xml news.xml
xdocs/common active-developers.xml branches.xml
code-standards.xml contributors.xml deprecation.xml
faq.xml issue-tracking.xml license.xml powered.xml
xdocs/images logo.gif
xdocs/stylesheets project.xml
Log:
start moving common docs to the turbine-site repository
Revision Changes Path
1.1 jakarta-turbine-site/README.txt
Index: README.txt
===================================================================
$Id: README.txt,v 1.1 2001/08/01 18:55:56 mpoeschl Exp $
The Jakarta Turbine Website Instructions
----------------------------------------
***NOTE***
DO NOT EDIT THE .html files in the docs directory.
Please follow the directions below for updating the website.
***NOTE***
The Turbine web site is based on .xml files which are transformed
into .html files using Anakia. Anakia is simply an Ant task that
performs the transformations using JDOM and Velocity.
<http://www.jdom.org/>
<http://jakarta.apache.org/velocity/>
<http://jakarta.apache.org/velocity/anakia.html>
In order to make modifications to the Turbine web site, you need
to first check out the jakarta-site2 and jakarta-turbine-site modules from CVS:
cvs -d /home/cvs login
cvs -d /home/cvs co jakarta-site2
cvs -d /home/cvs co jakarta-turbine-site
Once you have the site checked out locally, cd into your
jakarta-Turbine-site directory and execute:
ant
This will build the documentation into the docs/ directory. The output
will show you which files got re-generated.
If you would like to make modifications to the web site documents,
you simply need to edit the files in the xdocs/ directory.
The files in xdocs/stylesheets are the global files for the site. If you make a
modification to project.xml, it will affect the left side navigation for the
web site and all of your .html files will be re-generated. style.vsl is the
template that controls the look and feel for the overall web site. Editing
this file will also cause all of the .html files to be re-generated as well.
Once you have built your documentation and confirmed that your changes are
ok, you can check your .xml and your .html files back into CVS.
Then, in the /www/jakarta.apache.org/turbine/ directory, you can do a
cvs update -d -P
to have the changes reflected on the Turbine web site.
1.1 jakarta-turbine-site/build.properties
Index: build.properties
===================================================================
# -------------------------------------------------------------------
# B U I L D P R O P E R T I E S
# -------------------------------------------------------------------
# These properties are used by the Turbine build, you may override
# any of these default values by placing property values in
# your ${user.home}/build.properties file.
# -------------------------------------------------------------------
jakarta.site2 = ../jakarta-site2
docs.src = xdocs
docs.dest = docs
1.1 jakarta-turbine-site/build.xml
Index: build.xml
===================================================================
<?xml version="1.0"?>
<!-- Build file for Turbine -->
<project name="Turbine-site" default="docs" basedir=".">
<!-- Give user a chance to override without editing this file
(and without typing -D each time they invoke a target) -->
<!-- Set default values for the build -->
<property file="build.properties" />
<!-- Allow any user specific values to override the defaults -->
<property file="${user.home}/build.properties" />
<property name="jdom.jar" value="jdom-b6.jar"/>
<property name="jakarta.site2" value="../jakarta-site2"/>
<!-- ================================================================== -->
<!-- Make Turbine documentation -->
<!-- ================================================================== -->
<target name="check_for_jdom">
<available
property="jdom.present"
classname="org.jdom.JDOMException">
<classpath>
<pathelement location="${jakarta.site2}/lib/${jdom.jar}"/>
</classpath>
</available>
</target>
<target depends="check_for_jdom" name="docs-prepare-error"
unless="jdom.present">
<echo>
The Jakarta-Site2 module is not present! Please check
to make sure that you have checked it out from CVS.
<http://jakarta.apache.org/site/jakarta-site2.html>
</echo>
</target>
<target name="docs"
depends="docs-prepare-error"
description="--> generates the HTML documentation"
if="jdom.present">
<taskdef name="anakia"
classname="org.apache.velocity.anakia.AnakiaTask">
<classpath>
<fileset dir="${jakarta.site2}/lib">
<include name="*.jar"/>
</fileset>
</classpath>
</taskdef>
<anakia
basedir="${docs.src}"
destdir="${docs.dest}/"
extension=".html" style="./site.vsl"
projectFile="stylesheets/project.xml"
excludes="**/stylesheets/** empty.xml"
includes="**/*.xml"
lastModifiedCheck="true"
templatePath="${jakarta.site2}/xdocs/stylesheets">
</anakia>
<copy todir="${docs.dest}/images" filtering="no">
<fileset dir="${docs.src}/images">
<include name="**/*.gif"/>
<include name="**/*.jpeg"/>
<include name="**/*.jpg"/>
</fileset>
</copy>
<!-- In case we have CSS someday
<copy todir="${docs.dest}" filtering="no">
<fileset dir="${docs.src}">
<include name="**/*.css"/>
</fileset>
</copy>
-->
</target>
</project>
1.1 jakarta-turbine-site/xdocs/index.xml
Index: index.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="mpoeschl@marmot.at">Martin Poeschl</author>
<title>Jakarta Turbine</title>
</properties>
<body>
<section name="Jakarta Turbine">
<p>
Turbine is a servlet based framework that allows experienced Java
developers to quickly build secure web applications. Parts of
Turbine can also be used independently of the web portion of Turbine
as well. In other words, we strive to make portions of Turbine
easily available for use in other applications.
</p>
<p>
Turbine is developed in an open and participatory environment and
released under the <a href="http://www.apache.org/licenses">Apache
Software License</a>. Turbine is intended to be a collaboration of the
best-of-breed developers from around the world. We invite you to
participate in this open development project. To learn more about getting
involved, <a href="/site/getinvolved.html">click here</a>.
</p>
</section>
<section name="Turbine Versions">
<p>
There are several versions of Turbine currently available for download.
</p>
<p>
<strong>Turbine 2.1.x</strong>. Turbine 2.1 is the current production
quality release. The 2.1.x branch will continue in maintenance mode, but
no new feature releases are planned.</p>
<p>
<strong>Turbine 3.0</strong>.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/news.xml
Index: news.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="mpoeschl@marmot.at">Martin Poeschl</author>
<title>New and Status</title>
</properties>
<body>
<section name="News & Status">
<h3>4 June 2001 - Jakarta Turbine 2.1 Released</h3>
<p>
The <a href="http://jakarta.apache.org/turbine/">Turbine</a> Team
is proud to announce the 2.1 release of Turbine.
This release includes a new version of the
<a href="http://jakarta.apache.org/turbine/howto/tdk-howto.html">
Turbine Developer's Kit</a> and a new stand-alone version of
<a href="http://jakarta.apache.org/turbine/howto/torque-howto.html">Torque</a>.
You can find everything
<a href="http://jakarta.apache.org/builds/jakarta-turbine/release/2.1">here</a>.
</p>
<hr noshade="" size="1"/>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/active-developers.xml
Index: active-developers.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Active Developers</title>
<author email="rafal@apache.org">Rafal Krzewski</author>
</properties>
<body>
<section name="Active Developers">
<p>
This list includes people who have been committing code to the turbine
CVS in the last few months. Below each person's name, there is listed
code sections they have been active in.
</p>
<p>
Feel free to modify this list, by adding yourself if you are not
included, adding code sections below your name if you feel compenent in
them, are willing to review patches regarding this code, or fix problems
and add features yourself. Also, feel free to give away any code section
you are not interested in.
</p>
<b>Mr. Nobody</b>
<ul>
<li>Naming Service</li>
<li>Castor Service</li>
</ul>
<b><a href="mailto:daveb@miceda-data.com">Dave Bryson</a></b>
<ul>
<li>Scheduler Service</li>
<li>Cache Service</li>
</ul>
<b><a href="mailto:Gonzalo.Diethelm@iname.com">Gonzalo Diethelm</a></b>
<ul>
</ul>
<b><a href="mailto:chrise@scardini.com">Christopher Elkins</a></b>
<ul>
</ul>
<b><a href="mailto:rafal@apache.org">Rafal Krzewski</a></b>
<ul>
<li>Services framework</li>
<li>Upload Service</li>
<li>Security Service</li>
<li>Logging Service (with Tomasz Zielinski)</li>
<li>Resources Service (with Raphael Luta)</li>
<li>UniqueID Service</li>
</ul>
<b><a href="mailo:sean@informage.net">Sean Legassick</a></b>
<ul>
<li>Pull Service</li>
<li>Turbine Servlet</li>
<li>Parser Utilities</li>
</ul>
<b><a href="mailto:leon@opticode.co.za">Leon Messerschmidt</a></b>
<ul>
<li>XSLT Service</li>
<li>AssemberBroker Service</li>
<li>JPython integration</li>
</ul>
<b><a href="mailto:jmcnally@collab.net">John McNally</a></b>
<ul>
<li>Peers</li>
<li>Intake</li>
<li>Torque</li>
<li>Template Service</li>
</ul>
<b><a href="mailto:mpoeschl@marmot.at">Martin Poeschl</a></b>
<ul>
<li>Jyve</li>
<li>Security Service</li>
<li>TDK</li>
</ul>
<b><a href="mailto:ipriha@surfeu.fi">Ilkka Priha</a></b>
<ul>
<li>Pool Service</li>
<li>Factory Service</li>
<li>RunData Service</li>
<li>MimeType Service</li>
</ul>
<b><a href="mailto:dlr@collab.net">Daniel Rall</a></b>
<ul>
<li>PoolBroker Service</li>
<li>ConnectionPool</li>
<li>WebMacro Service</li>
</ul>
<b><a href="mailto:CRiley@ekmail.com">Cameron Riley</a></b>
<ul>
<li>Documentation</li>
</ul>
<b><a href="mailto:jon@latchkey.com">Jon Stevens</a></b>
<ul>
<li>A bit of everything</li>
<li>Localization Service</li>
</ul>
<b><a href="mailto:john@zenplex.com">John Thorhauer</a></b>
<ul>
<li>Scheduler Service</li>
</ul>
<b><a href="mailto:magnus@handtolvur.is">Magnús þór Torfason</a></b>
<ul>
<li>XML-RPC Service</li>
<li>Misc. locale support</li>
</ul>
<b><a href="mailto:jvanzyl@apache.org">Jason van Zyl</a></b>
<ul>
<li>TDK</li>
<li>Flux</li>
<li>Velocity Service</li>
<li>Pull Service</li>
<li>Servlet Service</li>
<li>Torque</li>
<li>Services Framework</li>
<li>Template Service</li>
<li>XML-RPC Service</li>
<li>Security Service (LDAP)</li>
<li>Resources Service</li>
</ul>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/branches.xml
Index: branches.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine CVS Branches</title>
<author email="rafal@apache.org">Rafal Krzewski</author>
</properties>
<body>
<section name="CVS Branches">
<p>
The branches are a feature of CVS that allows the development to be partitioned
so that one stream does not affect the other. They prove to be useful, when
there is a need to perform modifications that are hard to perform as a
consecutive gradual transitions that work well in the usual course of
development. When files that are depended upon by numerous other files need to
be substantially changed all the other would have to be modified along with
them. That would require that a lone developer performs all these changes in his
own snapshot and then checks them all in, causing the sources to leap forward.
As Turbine grows, situations arise that this is no longer possible. It's good to
have version control on the gradual changes as opposed to quantum-leap changes.
It's also important to have the larges set of eyes possible looking at the code
as soon as possible. On the other hand, we strive to keep Turbine CVS tree
compilable and working at all times. This calls for usage of branches whenever
vast modifications of the sources are needed.
</p>
<p>
The <a href="http://www.red-bean.com/cvsbook/">CVS book</a> describes multiple
approaches to performing development using branches. We decided that the
simplest approach called <em>Flying Fish technique</em> will fit our needs best.
It involves creating a branch when there is a need for a separate thread of
development, and abandoning the branch once all the changes are merged with the
trunk. If need arises for separated develompent on the same subject, a brand new
branch is creted. This saves us the additional complexity of merging changes
back and forth between the trunk and the branches and keeping track of what was
merged into where. We want the things to be as simple as possible.
</p>
<p>
The naming scheme used for the branches is as following: The name of the branch
is composed of a name describing the subject being worked on, followed by an
underscore and a two digit number used to distinguish multiple branches for the
same subject.<br/>
Actual tag names are then:<br/>
<em>subject</em>_<em>number</em>-sprout for marking the revision of the trunk
where the branch diverged <br/>
<em>subject</em>_<em>number</em>-branch for the branch itself <br/>
<em>subject</em>_<em>numner</em>-before-merge for marking the last revision of
files before merging in the branch <br/>
<em>subject</em>_<em>number</em>-merge for marking the revision of the trunk
with changes made on the branch merged in <br/>
</p>
<p>
Below, you can find a list of branches that were used during the development of
Turbine. The 'coordinating person' is responsible for exchange of information
between developers, maintaing the branches' TODO and timely merging the changes
into the trunk (closing the branch). The shorter a branch stays outside the
trunk, the better, because that decrases the number of conflict that will arise
while merging back. Developers that are working on the trunk of the CVS should
not make modifications to the code named in 'affected sources' to prevent
merging conflicts. Instead, they should direct all requests / patches to the
coordinating person. Developers wishing to join the development of the branching
code, should contact the coordinating person.
</p>
<p>
If you wish to learn more about branches, download the CVS book at
<a href="http://www.red-bean.com/cvsbook/">Red Bean.com</a>, or browse a
<a href="http://www.durak.org/cvswebsites/doc/cvs_5.php3#SEC54">CVS manual</a>
online.
</p>
</section>
<section name="Existing branches">
<table>
<tr>
<td>Repository</td>
<td><strong>jakarta-turbine</strong></td>
</tr>
<tr>
<td>Name</td>
<td><strong>security_01</strong></td>
</tr>
<tr>
<td>Status</td>
<td><strong>closed</strong></td>
</tr>
<tr>
<td>Date created</td>
<td>Sep 29 2000</td>
</tr>
<tr>
<td>Date closed</td>
<td>Nov 19 2000</td>
</tr>
<tr>
<td>Subject</td>
<td>Refactoring the security infrastructure of Turbine.</td>
</tr>
<tr>
<td>Coordinating person</td>
<td>Rafal Krzewski, <link href="mailto:Rafal.Krzewski@e-point.pl">
Rafal.Krzewski@e-point.pl</link></td>
</tr>
<tr>
<td>Affected sources</td>
<td>services.security, om.security, util.security packages,
TurbineMapBuilder class and other classes that use the security system</td>
</tr>
</table>
<table>
<tr>
<td>Repository</td>
<td><strong>jakarta-turbine</strong></td>
</tr>
<tr>
<td>Name</td>
<td><strong>T_2_1_BRANCH</strong></td>
</tr>
<tr>
<td>Status</td>
<td><strong>open</strong></td>
</tr>
<tr>
<td>Date created</td>
<td>May 3 2001</td>
</tr>
<tr>
<td>Date closed</td>
<td>n/a</td>
</tr>
<tr>
<td>Subject</td>
<td>Starting beta cycle for June 4th release.</td>
</tr>
<tr>
<td>Coordinating person</td>
<td>Jason van Zyl, <link href="mailto:jvanzyl@apache.org">
jvanzyl@apache.org</link></td>
</tr>
<tr>
<td>Affected sources</td>
<td>All sources</td>
</tr>
</table>
<table>
<tr>
<td>Repository</td>
<td><strong>jakarta-turbine-flux</strong></td>
</tr>
<tr>
<td>Name</td>
<td><strong>T_2_1_BRANCH</strong></td>
</tr>
<tr>
<td>Status</td>
<td><strong>open</strong></td>
</tr>
<tr>
<td>Date created</td>
<td>July 6 2001</td>
</tr>
<tr>
<td>Date closed</td>
<td>n/a</td>
</tr>
<tr>
<td>Subject</td>
<td>Branch for Turbine 2.1.x updates.</td>
</tr>
<tr>
<td>Coordinating person</td>
<td>Jason van Zyl, <link href="mailto:jvanzyl@apache.org">
jvanzyl@apache.org</link></td>
</tr>
<tr>
<td>Affected sources</td>
<td>All sources</td>
</tr>
</table>
<p>
You can check out any of the open branches listed above.
For example, if you wish to look at the source for the 2.1
branch then you would use the following command:
</p>
<source>
cvs co -d jakarta-turbine-2.1 -r T_2_1_BRANCH jakarta-turbine
</source>
<p>
This will check out the turbine 2.1 branch into a directory
called 'jakarta-turbine-2.1' so that it won't interfere with
the HEAD branch.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/code-standards.xml
Index: code-standards.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Coding Standards</title>
<author email="jon@latchkey.com">Jon S. Stevens</author>
<author email="jvanzyl@apache.org">Jason van Zyl</author>
</properties>
<body>
<section name="Coding Standards">
<p>
This document describes a list of coding conventions that are required
for code submissions to the project. By default, the coding conventions
for most Open Source Projects should follow the existing coding conventions
in the code that you are working on. For example, if the bracket is on
the same line as the if statement, then you should write all your code
to have that convention.
</p>
<p>
<strong>If you commit code that does not follow these conventions and you
are caught, you are responsible for also fixing your own code.</strong>
</p>
<p>
Below is a list of coding conventions that are specific to Turbine,
everything else not specificially mentioned here should follow the official
<a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Sun
Java Coding Conventions</a>.
</p>
<p>
1. Brackets should begin and end on a new line and should exist even
for one line statements. Examples:
</p>
<source test=""><![CDATA[
if ( foo )
{
// code here
}
try
{
// code here
}
catch (Exception bar)
{
// code here
}
finally
{
// code here
}
while ( true )
{
// code here
}
]]></source>
<p>
2. It is <strong>OK</strong> to have spaces between the parens or not. The
preference is to not include the extra spaces. For example, both of these are
ok:
</p>
<source test=""><![CDATA[
if (foo)
or
if ( foo )
]]></source>
<p>
3. 4 spaces. <strong>NO</strong> tabs. Period. We understand that a lot of you
like to use tabs, but the fact of the matter is that in a distributed
development enviroment, when the cvs commit messages get sent to a mailing list,
they are almost impossible to read if you use tabs.
</p>
<p>
In Emacs-speak, this translates to the following command:
(setq-default tab-width 4 indent-tabs-mode nil)
</p>
<p>
4. Unix linefeeds for all .java source code files. Other platform specific
files should have the platform specific linefeeds.
</p>
<p>
5. Javadoc <strong>MUST</strong> exist on all your methods. Also, if you are
working on existing code and there currently isn't a javadoc for that
method/class/variable or whatever, then you should contribute and add it.
This will improve the project as a whole.
</p>
<p>
6. The Jakarta/Turbine License <strong>MUST</strong> be placed at the top
of each and every file.
</p>
<p>
7. If you contribute to a file (code or documentation), add yourself to the
authors list at the top of the file. For java files the
preferred Javadoc format is:
</p>
<source><![CDATA[
@author <a href="mailto:user@domain.com">John Doe</a>
]]></source>
<p>
8. All .java files should have a @version tag like the one below.
</p>
<source><![CDATA[
@version $Id: code-standards.xml,v 1.1 2001/08/01 18:55:57 mpoeschl Exp $
]]></source>
<p>
9. Import statements must be fully qualified for clarity.
</p>
<source><![CDATA[
import java.util.ArrayList;
import java.util.Hashtable;
import org.apache.foo.Bar;
import org.apache.bar.Foo;
]]></source>
<p>
And not
</p>
<source><![CDATA[
import java.util.*;
import org.apache.foo.*;
import org.apache.bar.*;
]]></source>
<hr noshade="true" size="1"/>
<p>
X/Emacs users might appreciate this in their .emacs file.
</p>
<source><![CDATA[
(defun apache-jakarta-mode ()
"The Java mode specialization for Apache Jakarta projects."
(if (not (assoc "apache-jakarta" c-style-alist))
;; Define the Apache Jakarta cc-mode style.
(c-add-style "apache-jakarta" '("java" (indent-tabs-mode . nil))))
(c-set-style "apache-jakarta")
(c-set-offset 'substatement-open 0 nil)
(setq mode-name "Apache Jakarta")
;; Turn on syntax highlighting when X is running.
(if (boundp 'window-system)
(progn (setq font-lock-support-mode 'lazy-lock-mode)
(font-lock-mode t))))
;; Activate Jakarta mode.
(if (fboundp 'jde-mode)
(add-hook 'jde-mode-hook 'apache-jakarta-mode)
(add-hook 'java-mode-hook 'apache-jakarta-mode))
]]></source>
<p>
Thanks for your cooperation.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/contributors.xml
Index: contributors.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine Contributors</title>
<author email="jon@latchkey.com">Jon S. Stevens</author>
</properties>
<body>
<section name="Contributors">
<p>
The people listed below have made significant contributions to Turbine by
working long and hard to make quality software for the rest of the world to use.
</p>
<p>
Contributors to the Turbine Project should be extremely proud of themselves.
</p>
<p>
If you would like to become a contributor, please see the
<a href="todo.html">Todo</a> document to find areas where you
can contribute effectively. If there is nothing in there that suits your
interest, but you still have ideas, please feel free to suggest them on
the mailing list.
</p>
<p>
We are following a certification scheme like the one that is outlined here:
<a href="http://www.advogato.org/certs.html">http://www.advogato.org/certs.html</a>
</p>
<table>
<tr>
<td>Gary Bartlett</td>
<td><a href="mailto:gary_a_bartlett@yahoo.com">gary_a_bartlett@yahoo.com</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Jeffrey D. Brekke</td>
<td><a href="mailto:ekkerbj@netscape.net">ekkerbj@netscape.net</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Dave Bryson</td>
<td><a href="mailto:mbryson@mont.mindspring.com">mbryson@mont.mindspring.com</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Kevin A. Burton</td>
<td><a href="mailto:burton@relativity.yi.org">burton@relativity.yi.org</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Youngho Cho</td>
<td><a href="mailto:youngho@nannet.co.kr">youngho@nannet.co.kr</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Frank Conradie</td>
<td><a href="mailto:frank@opticode.co.za">frank@opticode.co.za</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Christopher Elkins</td>
<td><a href="mailto:celkins@scardini.com">celkins@scardini.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Gonzalo A. Diethelm</td>
<td><a href="mailto:gonzalo.diethelm@iname.com">gonzalo.diethelm@iname.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>David Duddleston</td>
<td><a href="mailto:david@i2a.com">david@i2a.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Jian He</td>
<td><a href="mailto:hjnet@163.net">hjnet@163.net</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Nissim Karpenstein</td>
<td><a href="mailto:nissim@nksystems.com">nissim@nksystems.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Chris Kimpton</td>
<td><a href="mailto:kimptoc.mail@bigfoot.com">kimptoc.mail@bigfoot.com</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Frank Kim</td>
<td></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Rafal Krzewski</td>
<td><a href="mailto:krzewski@e-point.pl">krzewski@e-point.pl</a></td>
<td><a href="http://www.e-point.pl/en">e-point S.A.</a></td>
<td>Master</td>
</tr>
<tr>
<td>Sean Legassick</td>
<td><a href="mailto:sean@informage.net">sean@informage.net</a></td>
<td><a href="http://www.informage.net">informage</a></td>
<td>Master</td>
</tr>
<tr>
<td>Josh Lucas</td>
<td><a href="mailto:josh@stonecottage.com">josh@stonecottage.com</a></td>
<td>CollabNet</td>
<td>Journeyer</td>
</tr>
<tr>
<td>Carl Ludewig</td>
<td><a href="mailto:">carl@destinymusic.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Jonas Maurus</td>
<td><a href="mailto:jm@mediaphil.de">jm@mediaphil.de</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Brett McLaughlin</td>
<td><a href="mailto:bmclaugh@algx.net">bmclaugh@algx.net</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>John Mcnally</td>
<td><a href="mailto:jmcnally@collab.net">jmcnally@collab.net</a></td>
<td>CollabNet</td>
<td>Master</td>
</tr>
<tr>
<td>Leon Messerschmidt</td>
<td><a href="mailto:leon@opticode.co.za">leon@opticode.co.za</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Chris Meyer</td>
<td><a href="mailto:cmeyer@gatan.com">cmeyer@gatan.com</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Stephan Nagy</td>
<td><a href="mailto:snagy@web-publicity.com">snagy@web-publicity.com</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Kasper Nielsen</td>
<td><a href="mailto:kav@kav.dk">kav@kav.dk</a></td>
<td>Metier</td>
<td>Journeyer</td>
</tr>
<tr>
<td>Paul O'Leary</td>
<td><a href="mailto:paul@evolventtech.com">paul@evolventtech.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Giacomo Pati</td>
<td><a href="mailto:Giacomo.Pati@pwr.ch">Giacomo.Pati@pwr.ch</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Martin Poeschl</td>
<td><a href="mailto:mpoeschl@marmot.at">mpoeschl@marmot.at</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Mark Porter</td>
<td><a href="mailto:mark.porter@canlink.com">mark.porter@canlink.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Jeff Prickett</td>
<td><a href="mailto:jeffprickett@mindspring.com">jeffprickett@mindspring.com</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Ilkka Priha</td>
<td><a href="mailto:ilkka.priha@simsoft.fi">ilkka.priha@simsoft.fi</a></td>
<td><a href="http://www.simsoft.fi">Simsoft</a></td>
<td>Master</td>
</tr>
<tr>
<td>Daniel L. Rall</td>
<td><a href="mailto:dlr@collab.net">dlr@collab.net</a></td>
<td>CollabNet</td>
<td>Master</td>
</tr>
<tr>
<td>Cameron Riley</td>
<td><a href="mailto:criley@ekmail.com">criley@ekmail.com</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>Greg Ritter</td>
<td><a href="mailto:greg@shwoop.com">greg@shwoop.com</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>Kurt Schrader</td>
<td><a href="mailto:kschrade@engin.umich.edu">kschrade@engin.umich.edu</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Ingo Schuster</td>
<td><a href="mailto:ingo@raleigh.ibm.com">ingo@raleigh.ibm.com</a></td>
<td></td>
<td>Apprentice</td>
</tr>
<tr>
<td>George Stewart</td>
<td><a href="mailto:georgestewart@yahoo.com">georgestewart@yahoo.com</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Costas Stergiou</td>
<td><a href="mailto:csterg@aias.gr">csterg@aias.gr</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Jon S. Stevens</td>
<td><a href="mailto:jon@latchkey.com">jon@latchkey.com</a></td>
<td>CollabNet</td>
<td>Master</td>
</tr>
<tr>
<td>Ralf Stranzenbach</td>
<td><a href="mailto:ralf@reswi.ruhr.de">ralf@reswi.ruhr.de</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Hakan Tandogan</td>
<td><a href="mailto:hakan42@gmx.de">hakan42@gmx.de</a></td>
<td></td>
<td>Journeyer</td>
</tr>
<tr>
<td>Scott C. Tavares</td>
<td><a href="mailto:stavares@home.com">stavares@home.com</a></td>
<td></td>
<td>Master</td>
</tr>
<tr>
<td>John Thorhauer</td>
<td><a href="mailto:john@zenplex.com">john@zenplex.com</a></td>
<td>Zenplex Inc.</td>
<td>Journeyer</td>
</tr>
<tr>
<td>Jason van Zyl</td>
<td><a href="mailto:jvanzyl@apache.org">jvanzyl@apache.org</a></td>
<td>Zenplex Inc.</td>
<td>Master</td>
</tr>
<tr>
<td>Magnús þór Torfason</td>
<td><a href="mailto:magnus@handpoint.com">magnus@handpoint.com</a></td>
<td><a href="http://www.handpoint.com/">handPoint</a></td>
<td>Apprentice</td>
</tr>
</table>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/deprecation.xml
Index: deprecation.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine Deprecation Policy</title>
<author email="jon@latchkey.com">Jon S. Stevens</author>
</properties>
<body>
<section name="Turbine Deprecation Policy">
<p>
In order for people to be comfortable with development of code based on
Turbine and not have to constantly worry about the rug being pulled out
from underneath them, we have instituted the following policy. Our goal
is to take this matter as an extremely serious practice.
</p>
</section>
<section name="The Rules">
<p>
<ol>
<li>
<strong>ALL</strong> existing class and method modification needs to go
through a deprecation phase. We realize that this may make some of the
API code look a bit ugly when you look at the source code, but this is a
MUST have. It is recommend that developers who deprecate methods move
them to the bottom of the .java file.
</li>
<li>
<p>
The amount of time between deprecation and removal must be at least one
release of Turbine. It could be more than one version release before the
deprecated item is removed, but it cannot be less than one version
release. In other words, we can deprecate something in 2.1 and remove it
in the release of 2.1.1. The amount of time between 2.1 and 2.1.1 could
be measured in days, not months. Discussion will occur on the mailing
list pertaining to the real number of versions between deprecation and
removal. You will have a chance to express your concerns and we will
take them into consideration. Most likely a major feature change will
not be removed between a 2.1 and 2.1.1 release. Instead, we would wait
until 2.2 to remove the deprecated items in that case.
</p>
<p>
The reason why we do not feel that time is of importance is because 6
months may not be a long enough time for a project to keep up and 2
weeks might be fine for another project. By focusing on deprecation
through releases, people can choose to code against a specific version
of Turbine and feel comfortable that their code will compile for at
least one released version. This also gives people the chance to compile
against various previous releases to do incremental upgrades and find
out what will break in the next release.
</p>
</li>
<li>
Any time a method is deprecated, notification <strong>MUST</strong> be
sent to the developer mailing list documenting the methods that have
been deprecated as well as the alternative use. This will allow people
to search the archives and find out when and why a method was deprecated
as well as the procedure for upgrading to the latest methodology.
</li>
<li>
Items that are not Java code related and cannot be deprecated (such as
property key changes and DTD modifications) must be documented on the
mailing list.
</li>
<li>
All documentation must be updated at the time of modification to reflect
the latest status of the code.
</li>
<li>
Any patches or commits that do not follow these rules will be rejected
and it is up to the person who has either checked in the modifications
or sent the patch to submit a new patch, fix the problem or back the
code out of CVS.
</li>
</ol>
</p>
</section>
<section name="Developers: Suggestions for following The Rules">
<p>
When changing the signature of a public or protected method or class,
this has the potential of breaking someones code who depends on the
method or class. Since we are developing Open Source software, there is
absolutely no way we can tell if someone is using our code or not.
Therefore, in order to minimize the effect of changes, it is possible
to use the concept of deprecation. When working on code, keep in mind
the following guidelines:
</p>
<p>
<ul>
<li>
When modifing an existing public or protected method or class
first mark the existing method as deprecated and create a new
one to replace the old one.
</li>
<li>
Do not remove any public or protected classes/interfaces that
have any chance of being used outside of the application.
Instead, mark them as deprecated.
</li>
<li>
When migrating code from one package to another, deprecate the
old package and then have the old code reference the new code as
a thin temporary wrapper. The deprecation tells people that the
wrapper will be going away at some point in the future.
</li>
<li>
Changes to configuration files needs to be well documented so
that people can have a laundry list of foo->bar conversions.
</li>
<li>
When changing a database schema, make sure to provide ALTER
TABLE statements to modify the schema so that people can convert
their existing databases easily.
</li>
</ul>
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/faq.xml
Index: faq.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine FAQ</title>
<author email="jvanzyl@apache.org">Jason van Zyl</author>
</properties>
<body>
<section name="Frequently Asked Questions">
<p>
Please refer to our <a href="http://java.apache.org/jyve-faq/Turbine/screen/DisplayTopics/action/SetAll/project_id/1/faq_id/2">
FAQ</a> housed in <a href="http://java.apache.org/jyve/">Jyve</a>.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/issue-tracking.xml
Index: issue-tracking.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Issue Tracking</title>
<author email="jvanzyl@apache.org">Jason van Zyl</author>
</properties>
<body>
<section name="Issue Tracking">
<p>
If you have found what you believe to be an issue with Turbine, please
report the issue using Bugzilla. You can report issues with Turbine
<a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Turbine">here</a>.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/license.xml
Index: license.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Apache Software License</title>
<author email="jvanzyl@apache.org">Jason van Zyl</author>
</properties>
<body>
<section name="Apache Software License">
<source test=""><![CDATA[
/* ====================================================================
* The Apache Software License, Version 1.1
*
* Copyright (c) 2001 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. The end-user documentation included with the redistribution,
* if any, must include the following acknowledgment:
* "This product includes software developed by the
* Apache Software Foundation (http://www.apache.org/)."
* Alternately, this acknowledgment may appear in the software itself,
* if and wherever such third-party acknowledgments normally appear.
*
* 4. The names "Apache" and "Apache Software Foundation" and
* "Apache Turbine" must not be used to endorse or promote products
* derived from this software without prior written permission. For
* written permission, please contact apache@apache.org.
*
* 5. Products derived from this software may not be called "Apache",
* "Apache Turbine", nor may "Apache" appear in their name, without
* prior written permission of the Apache Software Foundation.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
* ====================================================================
*
* This software consists of voluntary contributions made by many
* individuals on behalf of the Apache Software Foundation. For more
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
*/
]]></source>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/powered.xml
Index: powered.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine powered web sites</title>
<author email="jon@latchkey.com">Jon S. Stevens</author>
</properties>
<body>
<section name="Turbine powered web sites">
<p>
This is a list of public web sites that are created using Turbine
platform. This, of course, is by no means a complete listing of all
of the Turbine powered web sites.
</p>
<p>
<img src="images/powered-by-logo.gif" alt="powered-by-logo.gif" width="112" height="32" />
</p>
<p>
If you want your Turbine powered site listed here, please post a message on
the Turbine
<a href="http://jakarta.apache.org/site/mail.html">mailing list</a>.
</p>
<table>
<tr>
<td>URL</td>
<td>Type</td>
<td>Created By</td>
</tr>
<tr>
<td>
<a href="http://tambora.zenplex.org">tambora.zenplex.org</a>
</td>
<td>
Home of an OSS project.
</td>
<td>
<a href="http://www.zenplex.org">Zenplex</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.discuss.gr">www.discuss.gr</a>
(<a href="http://www.discuss.gr/deng/template/www,Category.vm/lang/2">english</a>)
</td>
<td>
A discussion site where anyone can start its own board or forum.
</td>
<td>
Costas Stergiou
</td>
</tr>
<tr>
<td>
<a href="http://www.flashcan.com">www.flashcan.com</a>
</td>
<td>
An interactive card making game using Turbine and Macromedia's
Flash5.
</td>
<td>
<a href="http://www.zincroe.com">ZincRoe</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.freeflats.co.uk">www.freeflats.co.uk</a>
</td>
<td>
Free Property advertisment / search for accomodation
</td>
<td>
Chris Kimpton
</td>
</tr>
<tr>
<td>
<a href="http://www.one.ee">www.one.ee</a><br/>
<a href="http://www.one.lv">www.one.lv</a><br/>
<a href="http://www.one.lt">www.one.lt</a>
</td>
<td>
Wireless messaging web application with PIM capabilities.
</td>
<td>
<a href="http://www.interakta.com">interakta</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.pfm.pl">www.pfm.pl</a>
</td>
<td>
A portal dedicated to health care
</td>
<td>
<a href="http://www.e-point.pl/en/">e-point S.A.</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.wbksa.pl">www.wbksa.pl</a>
</td>
<td>
A website of a major Polish bank
</td>
<td>
<a href="http://www.e-point.pl/en/">e-point S.A.</a>
</td>
</tr>
<tr>
<tr>
<td>
<a href="http://www.xmladvantage.com">www.xmladvantage.com</a>
</td>
<td>
XML news weblog
</td>
<td>
<a href="mailto:ealtman@xmladvantage.com">Eric J. Altman</a>
</td>
</tr>
<td>
<a href="http://www.zwut.com.pl">www.zwut.com.pl</a>
</td>
<td>
A website of the polish subsidiary of Siemens
</td>
<td>
<a href="http://www.e-point.pl/en/">e-point S.A.</a>
</td>
</tr>
</table>
</section>
<section name="Web sites using Turbine technology">
<p>
These web sites make use of Turbine features without having built
their entire site around Turbine.
</p>
<table>
<tr>
<td>URL</td>
<td>Type</td>
<td>Created By</td>
</tr>
<tr>
<td>
<a href="http://www.idendev.com">www.idendev.com</a>
</td>
<td>
Motorolla J2ME enabled mobile phone developer network.
</td>
<td>
<a href="http://www.collab.net">CollabNet</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.netbeans.org">www.netbeans.org</a>
</td>
<td>
Developer network for Sun Microsystem's open source IDE,
NetBeans.
</td>
<td>
<a href="http://www.collab.net">CollabNet</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.openadaptor.org">www.openadaptor.org</a>
</td>
<td>
Dresdner Kleinwort Wasserstein Bank OpenAdaptor developer
network. OpenAdaptor is enterprise application integration
software.
</td>
<td>
<a href="http://www.collab.net">CollabNet</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.openoffice.org">www.openoffice.org</a>
</td>
<td>
Developer network for Sun Microsystem's OpenOffice (previously
known as StarOffice).
</td>
<td>
<a href="http://www.collab.net">CollabNet</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.possenet.org">www.possenet.org</a>
</td>
<td>
Progress Software developer network for their Progress
Application Development Environment.
</td>
<td>
<a href="http://www.collab.net">CollabNet</a>
</td>
</tr>
<tr>
<td>
<a href="http://www.tigris.org">www.tigris.org</a>
</td>
<td>
Open source development tool suite.
</td>
<td>
<a href="http://www.collab.net">CollabNet</a>
</td>
</tr>
</table>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/images/logo.gif
<<Binary file>>
1.1 jakarta-turbine-site/xdocs/stylesheets/project.xml
Index: project.xml
===================================================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<project name="Jakarta Turbine Site"
href="http://jakarta.apache.org/turbine">
<title>The Jakarta Site</title>
<logo href="/images/logo.gif">The Jakarta Turbine Project</logo>
<body>
<menu name="Turbine">
<item name="Front Page" href="/index.html"/>
<item name="News & Status" href="/news.html"/>
</menu>
<menu name="Documentation">
<item name="Turbine 2.1" href="/turbine-2.1-doc/index.html"/>
<item name="Turbine 3.0" href="/turbine-3.0-doc/index.html"/>
</menu>
<menu name="Download">
<item name="Binaries" href="/site/binindex.html"/>
<item name="Source Code" href="/site/sourceindex.html"/>
</menu>
<menu name="Get Involved">
<item name="Contributors" href="/common/contributors.html"/>
<item name="CVS Repos" href="http://jakarta.apache.org/site/cvsindex.html"/>
<item name="FAQ" href="./common/faq.html"/>
<item name="Mailing Lists" href="http://jakarta.apache.org/site/mail.html"/>
<item name="Powered by Turbine" href="/common/powered.html"/>
<item name="License" href="/common/license.html"/>
<item name="Issue Tracking" href="/common/issue-tracking.html"/>
</menu>
<menu name="Development">
<item name="Active Developers" href="/common/active-developers.html"/>
<item name="Coding Specification" href="/common/code-standards.html"/>
<item name="CVS Branches" href="/common/branches.html"/>
<item name="Deprecation Rules" href="/common/deprecation.html"/>
</menu>
</body>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org