Mailing-List: contact continuum-commits-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r581928 - in
 /maven/continuum/branches/continuum-site_1.1/src/site: apt/community.apt
 apt/development/ apt/development/guide-continuum-development.apt
 apt/documentation/1_1/installation/release-notes.apt apt/guide-helping.apt
 site.xml
Date: Thu, 04 Oct 2007 14:37:17 -0000
To: continuum-commits@maven.apache.org
From: evenisse@apache.org
Message-Id: <20071004143718.C20A61A9832@eris.apache.org>

Author: evenisse
Date: Thu Oct  4 07:37:17 2007
New Revision: 581928

URL: http://svn.apache.org/viewvc?rev=581928&view=rev
Log: (empty)

Added:
    maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt   (with props)
    maven/continuum/branches/continuum-site_1.1/src/site/apt/development/
    maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt   (with props)
    maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt   (with props)
Modified:
    maven/continuum/branches/continuum-site_1.1/src/site/apt/documentation/1_1/installation/release-notes.apt
    maven/continuum/branches/continuum-site_1.1/src/site/site.xml

Added: maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt
URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt?rev=581928&view=auto
==============================================================================
--- maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt (added)
+++ maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt Thu Oct  4 07:37:17 2007
@@ -0,0 +1,53 @@
+ ----
+ The Continuum Community
+ -----
+ Eric Redmond
+ Emmanuel Venisse
+ -----
+ 17 October 2006
+ -----
+
+The Continuum Community
+
+  Continuum, like any other opensource project, relies heavily on the efforts of the entire user community
+  to be ever vigilent for improvements, logging of defects, communicating use-cases, generating
+  documentation, and being wary of other users in need. This is a quick guide outlining what
+  members of the Continuum community may do to make the system work better for everyone.
+
+* Helping With Continuum
+
+  There is already a comprehensive {{{guide-helping.html}Guide to Helping With Continuum}}.
+  That guide focuses upon beginning as a supporter, with information on how to help the coding effort.
+
+** Commit Questions or Answers to the Continuum User FAQ
+
+  Documentation is currently a very high priority for the Continuum community. Please help out where ever you can,
+  specifically in the work-in-progress {{{http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+FAQ}FAQ Wiki}}.
+
+** Help Log Defects in JIRA
+
+  Just as any other healthy project requires a quick turn-around on defects, and a transparent
+  method of users to have their wishes heard, so too does Continuum need your help.
+
+  * {{{http://jira.codehaus.org/browse/CONTINUUM}Continuum Defects, Improvements and Tasks}}
+
+  []
+
+** Developers
+
+  For Maven developers, commiters, PMC: there is a {{{http://maven.apache.org/developers/index.html}Developers Guide}}.
+
+* User Gathering Spots
+
+  These are a few of the watering holes around which Continuum users tend to gather.
+
+** Mailing Lists
+
+  Continuum has a number of {{{mail-lists.html}Mailing Lists}}, and a the Continuum User List is specifically dedicated to
+  answering questions about all things Continuum.
+
+** IRC
+
+  Log into the <<<#continuum>>> IRC channel on <<<irc.codehaus.org>>>. If you would like to access this over a web interface,
+  you can do so at {{http://irc.codehaus.org/}}.
+

Propchange: maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: maven/continuum/branches/continuum-site_1.1/src/site/apt/community.apt
------------------------------------------------------------------------------
    svn:keywords = "Author Date Id Revision"

Added: maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt
URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt?rev=581928&view=auto
==============================================================================
--- maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt (added)
+++ maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt Thu Oct  4 07:37:17 2007
@@ -0,0 +1,133 @@
+ ------
+ Guide to Developing Continuum
+ ------
+ Emmanuel Venisse
+ ------
+ October 2007
+ ------
+
+Developing Continuum
+
+    <<To write>>
+
+* {Creating and submitting a patch}
+
+ When you have either completed an issue or just want some feedback on the work you have done, create a patch
+ and attach the patch to the issue in question. We have a couple of guidelines when creating patches:
+
+ * Always create the patch from the root of the continuum project, i.e. where the pom.xml file is.
+
+ * If this was a new piece of work without a JIRA issue, create a JIRA issue for it now.
+
+ * Name the file <<<CONTINUUM-<issue number>-<artifact id>.patch>>>.
+
+ * Attach the patch to the JIRA issue you were working on (do not paste its content in as a comment though). 
+   When adding the patch add a comment to the issue explaining what it does. Shortly after, someone will apply the patch
+   and close the issue.
+
+ []
+
+ An example on how to create a patch from the command line:
+
+---
+$ svn diff > CONTINUUM-1234.patch
+---
+
+ If you are picking up an issue with a existing patch attached to the issue you can apply the patch to your working
+ directory directly from JIRA like this. The <<<wget>>> and <<<patch>>> commands will only be available if you are
+ on a UNIX platform or using Cygwin on windows.
+
+---
+$ wget -O - -q <URL to the patch from JIRA> | patch -p0
+---
+
+ If the patch is in a local file <<<CONTINUUM-1234.patch>>> and you want to apply that use this command:
+
+---
+$ patch -p0 < CONTINUUM-1234.patch
+---
+
+ A couple of notes:
+
+ * If you are using another tool for creating patches, make sure that the patch doesn't include absolute paths.
+ Including absolute paths in the patch will make the useless for us as we most likely don't have the same directory
+ structure as you.
+
+ * Make sure that you follow our code style.
+
+* Other useful Subversion commands while developing
+
+ If you've done a chunk of work and you would like ditch your changes and start from scratch use this command to
+ revert to the original checkout:
+
+---
+$ svn revert -R .
+---
+
+ The <<<-R>>> argument means that the command will recurse down all directories and revert all changes.
+
+ Before committing code to the Subversion repository we always set the <<<svn:ignore>>> property on the directory
+ to prevent some files and directories to be checked in. We always exclude the IDE project files and the <<<target/>>>
+ directory. Instead of keeping all of the excludes in mind all the time it's useful to put them all in a file and
+ reference the file with the <<<-F>>> option:
+
+---
+$ svn propset svn:ignore -F ~/bin/svnignore .
+---
+
+ An example svnignore file:
+
+---
+target
+*~
+*.log
+.classpath
+.project
+*.ipr
+*.iws
+*.iml
+---
+
+* Patch acceptance criteria
+
+There are a number of criteria that a patch will be judged on:
+
+  * Whether it works and does what is intended. This one is probably obvious!
+
+  * Whether it fits the spirit of the project. Some patches may be rejected as they take the project in a different
+    direction to that which the current development community has chosen. This is usually discussed on an issue well
+    before a patch is contributed, so if you are unsure, discuss it there or on the mailing lists first. Feel free to
+    continue discussing it (with new justification) if you disagree, or appeal to a wider audience on the mailing lists.
+
+  * Whether it contains tests. It is expected that any patches relating to functionality will be accompanied by unit tests
+    and/or integration tests. It is strongly desired (and will be requested) for bug fixes too, but will not be the basis
+    for not applying it. At a bare minimum, the change should not decrease the amount of automated test coverage.
+    As a community, we are focusing on increasing the current coverage, as there are several areas that do not receive automated testing.
+
+  * Whether it contains documentation. All new functionality needs to be documented for users, even if it is very rough
+    for someone to expand on later. While rough is acceptable, incomplete is not. As with automated testing, as a community
+    we are striving to increase the current coverage of documentation.
+
+Above all, don't be discouraged. These are the same requirements the current commiters should hold each other to as well.
+And remember, your contributions are always welcome!
+
+* {Commit Message Template}
+
+  Commits should have a message that follows this template:
+
+-----
+[issue1, issue2] <<comment>>
+Submitted by: (when it was a patch, put that persons name there)
+-----
+
+  <<issue>> can be omitted if there was no relevant JIRA issue, though it is strongly encouraged to create one for significant
+  changes.
+
+  <<Submitted by>> only needs to be specified when a patch is being applied for a non-committer.
+  
+eg:
+
+-----
+[CONTINUUM-1234] Added the foo to the bar
+Submitted by: Baz Bazman
+-----

Propchange: maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: maven/continuum/branches/continuum-site_1.1/src/site/apt/development/guide-continuum-development.apt
------------------------------------------------------------------------------
    svn:keywords = "Author Date Id Revision"

Modified: maven/continuum/branches/continuum-site_1.1/src/site/apt/documentation/1_1/installation/release-notes.apt
URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-site_1.1/src/site/apt/documentation/1_1/installation/release-notes.apt?rev=581928&r1=581927&r2=581928&view=diff
==============================================================================
--- maven/continuum/branches/continuum-site_1.1/src/site/apt/documentation/1_1/installation/release-notes.apt (original)
+++ maven/continuum/branches/continuum-site_1.1/src/site/apt/documentation/1_1/installation/release-notes.apt Thu Oct  4 07:37:17 2007
@@ -10,12 +10,16 @@
 
     The Continuum team is pleased to announce the Continuum 1.1-beta-3 release
     
-    Highlights are:
+    <<Highlights are:>>
     
       * lot of bug fixes
+      
       * xwork/webwork update to fix remote code exploit in forms
+      
       * mail notification to latest committers
+      
       * LDAP authentication
+      
       * performance improvement
     
     You can grab the latest release from:
@@ -26,132 +30,132 @@
     
     Below is the jira release notes for this release.
     
-    <<Release Notes - Continuum - Version 1.1-beta-3 :>>
+* Release Notes - Continuum - Version 1.1-beta-3 :
     
-    <<Sub-task>>
+** Sub-task
+
+    * [CONTINUUM-1441] - Keep connection on irc server between each messages
+
+** Bug
+
+    * [CONTINUUM-697] - sizes incompatible with mssql (Patch Attached)
     
-        * [CONTINUUM-1441] - Keep connection on irc server between each messages
+    * [CONTINUUM-1037] - Ant projects inherit a default build definition for Maven 2.
     
-    <<Bug>>
+    * [CONTINUUM-1038] - Build definitions should list what type they are (ant, maven, maven2, shell)
     
-        * [CONTINUUM-697] - sizes incompatible with mssql (Patch Attached)
-        
-        * [CONTINUUM-1037] - Ant projects inherit a default build definition for Maven 2.
-        
-        * [CONTINUUM-1038] - Build definitions should list what type they are (ant, maven, maven2, shell)
-        
-        * [CONTINUUM-1041] - two defaults on the build definition page
-        
-        * [CONTINUUM-1181] - Continuum aborts when running Postgres under JBoss
-        
-        * [CONTINUUM-1296] - Continuum 1.1-alpha-1 does not copy Maven2 project pom.xml's /project/build/defaultGoal/text() value to Build Definition Goals field.
-        
-        * [CONTINUUM-1306] - templated roles are not added automatically if missing after upgrade
-        
-        * [CONTINUUM-1325] - Surefire Report history is not kept for prior builds
-        
-        * [CONTINUUM-1348] - jut of memory in build result
-        
-        * [CONTINUUM-1367] - granting group admin rights for a single project doesn't seem to work
-        
-        * [CONTINUUM-1384] - Build error when enqueing happens during SCM update
-        
-        * [CONTINUUM-1391] - Missing "Download as text " link
-        
-        * [CONTINUUM-1393] - change sets are duplicated on multiple failed builds
-        
-        * [CONTINUUM-1395] - check the permissions on the add project action for ant projects
-        
-        * [CONTINUUM-1404] - M2 Multi module projects still build non-recursively
-        
-        * [CONTINUUM-1411] - Link to display build surefire report doesn't work (in fact displaying surefire report per build is false)
-        
-        * [CONTINUUM-1412] - File Inclusion Vulnerability
-        
-        * [CONTINUUM-1415] - Javascript errors with IE
-        
-        * [CONTINUUM-1417] - continuum group administrator role should imply user + developer too
-        
-        * [CONTINUUM-1418] - Groups Roles aren't added automatically at startup in the available roles list if the users list was deleted
-        
-        * [CONTINUUM-1420] - "Build Fresh" and Profile columns are missed in group build definitions page for specific project build definitions
-        
-        * [CONTINUUM-1423] - Default project group is missing from the list
-        
-        * [CONTINUUM-1428] - Continuum must rebuild automatically a project that was in error in the previous build even if it haven't changesin the current update
-        
-        * [CONTINUUM-1429] - Initial checkout does not respect 'Use cached scm credentials' setting
-        
-        * [CONTINUUM-1435] - Release prepare not working
-        
-        * [CONTINUUM-1439] - Group Summary page display error
-        
-        * [CONTINUUM-1445] - Impossible to add two projects with the same name even if they have differents version and/or scmUrl
-        
-        * [CONTINUUM-1448] - upgrade to last webwork/xwork
-    
-    <<Improvement>>
-    
-        * [CONTINUUM-406] - irc notifications: support for registered nicks
-        
-        * [CONTINUUM-522] - IRC support needed for IRC servers not supporting /privmsg
-        
-        * [CONTINUUM-1093] - After validation, logged in user is shown the login page
-        
-        * [CONTINUUM-1218] - Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase
-        
-        * [CONTINUUM-1278] - Need to add description and/or name to build defintion
-        
-        * [CONTINUUM-1279] - Need to add "Build Information" to the build result reports and notification.
-        
-        * [CONTINUUM-1333] - show in project group summary per project also the status counters (as they are shown on the project groups pages)
-        
-        * [CONTINUUM-1366] - surefire report shown is always latest, even with a different build number
-        
-        * [CONTINUUM-1394] - continuum should not record change sets when it is a new checkout
-        
-        * [CONTINUUM-1396] - Continuum should have a separate permission to administer schedules
-        
-        * [CONTINUUM-1409] - A build does not say which build definition it came from
-        
-        * [CONTINUUM-1422] - The icon for 'Cancel Build' is missing from the legend
-        
-        * [CONTINUUM-1424] - Ability to Cancel Build for a subset of a project group
-        
-        * [CONTINUUM-1425] - URL in Company Pom should open in a new Window
-        
-        * [CONTINUUM-1427] - Ability to choose the build definition for 'Build all projects' and 'Build Project(s)'
-        
-        * [CONTINUUM-1430] - Split forms for environment variables and Ant/Maven/JDK installations
-        
-        * [CONTINUUM-1440] - write documentation how to use continuum-data-management
-        
-        * [CONTINUUM-1443] - Add an 'Always build' checkbox in 'build definition'
-        
-        * [CONTINUUM-1444] - IRC and Jabber notifiers accept invalid ports.
-        
-        * [CONTINUUM-1446] - Webwork Performance Tuning
-        
-        * [CONTINUUM-1455] - In a project's working directory it would be nice to see a date and time...
-        
-        * [CONTINUUM-1478] - Place a "Check All / Check None" checkbox for projects
-    
-    <<New Feature>>
-    
-        * [CONTINUUM-358] - User Authentication via LDAP
-        
-        * [CONTINUUM-605] - Add a RecipientSource that derives addresses from the change list
-        
-        * [CONTINUUM-1207] - Need to be able to define default build definition used when adding new project
-    
-    <<Task>>
-    
-        * [CONTINUUM-1386] - Some data management modules use always plexus-security dependencies instead of redback
-        
-        * [CONTINUUM-1447] - To fix /bin/bash issue on some platform, update plexus-utils to 1.4.6
-    
-    <<Wish>>
-    
-        * [CONTINUUM-622] - Configure default build description
-        
-        * [CONTINUUM-1167] - Patch to add JBoss support
+    * [CONTINUUM-1041] - two defaults on the build definition page
+    
+    * [CONTINUUM-1181] - Continuum aborts when running Postgres under JBoss
+    
+    * [CONTINUUM-1296] - Continuum 1.1-alpha-1 does not copy Maven2 project pom.xml's /project/build/defaultGoal/text() value to Build Definition Goals field.
+    
+    * [CONTINUUM-1306] - templated roles are not added automatically if missing after upgrade
+    
+    * [CONTINUUM-1325] - Surefire Report history is not kept for prior builds
+    
+    * [CONTINUUM-1348] - jut of memory in build result
+    
+    * [CONTINUUM-1367] - granting group admin rights for a single project doesn't seem to work
+    
+    * [CONTINUUM-1384] - Build error when enqueing happens during SCM update
+    
+    * [CONTINUUM-1391] - Missing "Download as text " link
+    
+    * [CONTINUUM-1393] - change sets are duplicated on multiple failed builds
+    
+    * [CONTINUUM-1395] - check the permissions on the add project action for ant projects
+    
+    * [CONTINUUM-1404] - M2 Multi module projects still build non-recursively
+    
+    * [CONTINUUM-1411] - Link to display build surefire report doesn't work (in fact displaying surefire report per build is false)
+    
+    * [CONTINUUM-1412] - File Inclusion Vulnerability
+    
+    * [CONTINUUM-1415] - Javascript errors with IE
+    
+    * [CONTINUUM-1417] - continuum group administrator role should imply user + developer too
+    
+    * [CONTINUUM-1418] - Groups Roles aren't added automatically at startup in the available roles list if the users list was deleted
+    
+    * [CONTINUUM-1420] - "Build Fresh" and Profile columns are missed in group build definitions page for specific project build definitions
+    
+    * [CONTINUUM-1423] - Default project group is missing from the list
+    
+    * [CONTINUUM-1428] - Continuum must rebuild automatically a project that was in error in the previous build even if it haven't changesin the current update
+    
+    * [CONTINUUM-1429] - Initial checkout does not respect 'Use cached scm credentials' setting
+    
+    * [CONTINUUM-1435] - Release prepare not working
+    
+    * [CONTINUUM-1439] - Group Summary page display error
+    
+    * [CONTINUUM-1445] - Impossible to add two projects with the same name even if they have differents version and/or scmUrl
+    
+    * [CONTINUUM-1448] - upgrade to last webwork/xwork
+
+** Improvement
+
+    * [CONTINUUM-406] - irc notifications: support for registered nicks
+    
+    * [CONTINUUM-522] - IRC support needed for IRC servers not supporting /privmsg
+    
+    * [CONTINUUM-1093] - After validation, logged in user is shown the login page
+    
+    * [CONTINUUM-1218] - Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase
+    
+    * [CONTINUUM-1278] - Need to add description and/or name to build defintion
+    
+    * [CONTINUUM-1279] - Need to add "Build Information" to the build result reports and notification.
+    
+    * [CONTINUUM-1333] - show in project group summary per project also the status counters (as they are shown on the project groups pages)
+    
+    * [CONTINUUM-1366] - surefire report shown is always latest, even with a different build number
+    
+    * [CONTINUUM-1394] - continuum should not record change sets when it is a new checkout
+    
+    * [CONTINUUM-1396] - Continuum should have a separate permission to administer schedules
+    
+    * [CONTINUUM-1409] - A build does not say which build definition it came from
+    
+    * [CONTINUUM-1422] - The icon for 'Cancel Build' is missing from the legend
+    
+    * [CONTINUUM-1424] - Ability to Cancel Build for a subset of a project group
+    
+    * [CONTINUUM-1425] - URL in Company Pom should open in a new Window
+    
+    * [CONTINUUM-1427] - Ability to choose the build definition for 'Build all projects' and 'Build Project(s)'
+    
+    * [CONTINUUM-1430] - Split forms for environment variables and Ant/Maven/JDK installations
+    
+    * [CONTINUUM-1440] - write documentation how to use continuum-data-management
+    
+    * [CONTINUUM-1443] - Add an 'Always build' checkbox in 'build definition'
+    
+    * [CONTINUUM-1444] - IRC and Jabber notifiers accept invalid ports.
+    
+    * [CONTINUUM-1446] - Webwork Performance Tuning
+    
+    * [CONTINUUM-1455] - In a project's working directory it would be nice to see a date and time...
+    
+    * [CONTINUUM-1478] - Place a "Check All / Check None" checkbox for projects
+
+** New Feature
+
+    * [CONTINUUM-358] - User Authentication via LDAP
+    
+    * [CONTINUUM-605] - Add a RecipientSource that derives addresses from the change list
+    
+    * [CONTINUUM-1207] - Need to be able to define default build definition used when adding new project
+
+** Task
+
+    * [CONTINUUM-1386] - Some data management modules use always plexus-security dependencies instead of redback
+    
+    * [CONTINUUM-1447] - To fix /bin/bash issue on some platform, update plexus-utils to 1.4.6
+
+** Wish
+
+    * [CONTINUUM-622] - Configure default build description
+    
+    * [CONTINUUM-1167] - Patch to add JBoss support

Added: maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt
URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt?rev=581928&view=auto
==============================================================================
--- maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt (added)
+++ maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt Thu Oct  4 07:37:17 2007
@@ -0,0 +1,77 @@
+ ------
+ Guide to helping with Continuum
+ ------
+ Brett Porter
+ Jason van Zyl
+ Emmanuel Venisse
+ ------
+ 12 October 2005
+ ------
+
+Guide to helping with Continuum
+
+ As with any open source project, there are several ways you can help:
+
+ * Join the {{{mail-lists.html}mailing list}} and answer other user's questions
+
+ * Report bugs, feature requests and other issues in the {{{issue-tracking.html}issue tracking}} application.
+
+ * {{{documentation/1_1/developer_guides/building.html} Build Continuum}} for yourself, in order to fix bugs.
+
+ * {{{development/guide-continuum-development.html#Creating and submitting a patch}Submit patches}} to reported issues (both those you find, or that others have filed)
+
+ * Help with the documentation by pointing out areas that are lacking or unclear, and if you are so inclined, submitting patches to correct it.
+   You can quickly contribute rough thoughts to the {{{http://docs.codehaus.org/display/CONTINUUMUSER} wiki}}, or you can volunteer to help collate and
+   organise information that is already there.
+
+ []
+
+ Your participation in the community is much appreciated!
+
+Why Would I Want to Help?
+
+ There are several reasons these are good things.
+
+  * By answering other people's questions, you can learn more for yourself
+
+  * By submitting your own fixes, they get incorporated faster
+
+  * By reporting issues, you ensure that bugs don't get missed, or forgotten
+
+  * You are giving back to a community that has given you software for free
+
+How do I Join the Project?
+
+ Projects at Apache operate under a meritocracy, meaning those that the developers notice participating to a
+ high extent will be invited to join the project as a committer.
+
+ This is as much based on personality and ability to work with other developers and the community as it is with
+ proven technical ability. Being unhelpful to other users, or obviously looking to become a committer for bragging
+ rights and nothing else is frowned upon, as is asking to be made a committer without having contributed
+ sufficiently to be invited.
+
+Developers Conventions
+
+  There are a number of conventions used in the project, which contributors and developers alike should follow for
+  consistency's sake.
+
+  * {{{development/guide-continuum-development.html#Continuum Code Style} Code Style}}
+
+  * {{{development/guide-continuum-development.html#Commit Message Template} Commit Message Template}}
+
+Resources for committers
+
+  * {{{http://www.apache.org/dev/} Developer Resources}}
+
+  * {{{http://www.apache.org/foundation/} About the Apache Software Foundation}}
+
+  * {{{http://www.apache.org/dev/committers.html} Committer FAQ}}
+
+  * {{{http://people.apache.org/~vgritsenko/stats/projects/maven.html} Web Stats}}
+
+  * {{{http://people.apache.org/~coar/mlists.html#maven.apache.org} Mailing List Stats}}
+
+  * {{{http://wiki.apache.org} Apache Wiki}}
+
+
+

Propchange: maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: maven/continuum/branches/continuum-site_1.1/src/site/apt/guide-helping.apt
------------------------------------------------------------------------------
    svn:keywords = "Author Date Id Revision"

Modified: maven/continuum/branches/continuum-site_1.1/src/site/site.xml
URL: http://svn.apache.org/viewvc/maven/continuum/branches/continuum-site_1.1/src/site/site.xml?rev=581928&r1=581927&r2=581928&view=diff
==============================================================================
--- maven/continuum/branches/continuum-site_1.1/src/site/site.xml (original)
+++ maven/continuum/branches/continuum-site_1.1/src/site/site.xml Thu Oct  4 07:37:17 2007
@@ -62,48 +62,50 @@
           <item name="Upgrade" href="documentation/1_1/installation/upgrade.html"/>
       </item>
       <item name="User's Guides" collapse="true" href="documentation/1_1/user_guides/index.html">
-        <item name="Managing a Project" collapse="true">
-            <item name="Add a Project"/>
-            <item name="Edit a Project"/>
-            <item name="Remove a Project"/>
+        <item name="Managing a Project" href="documentation/1_1/user_guides/managing_project/index.html" collapse="true">
+            <item name="Add a Project" href="documentation/1_1/user_guides/managing_project/addProject.html"/>
+            <item name="Edit a Project" href="documentation/1_1/user_guides/managing_project/EditProject.html"/>
+            <item name="Remove a Project" href="documentation/1_1/user_guides/managing_project/RemoveProject.html"/>
             <!-- item name="SCM security hints"/ -->
         </item>
-        <item name="Managing Build Definitions">
-            <item name="Add a Project Build Definition"/>
-            <item name="Add a Project GroupBuild Definition"/>
-            <item name="Add a Build Definition Template"/>
+        <item name="Managing Build Definitions" href="documentation/1_1/user_guides/managing_builddef/index.html" collapse="true">
+            <item name="Project Build Definition" href="documentation/1_1/user_guides/managing_builddef/builddefProject.html"/>
+            <item name="Project Group Build Definition" href="documentation/1_1/user_guides/managing_builddef/builddefGroup.html"/>
+            <item name="Build Definition Template" href="documentation/1_1/user_guides/managing_builddef/builddefTemplate.html"/>
         </item>
         <item name="Managing Notification" href="documentation/1_1/user_guides/notification/index.html" collapse="true">
-            <item name="Mail Notification"/>
-            <item name="IRC Notification"/>
-            <item name="Jabber Notification"/>
-            <item name="MSN Notification"/>
-            <item name="Wagon Notification"/>
+            <item name="Mail Notification" href="documentation/1_1/user_guides/notification/mail.html"/>
+            <item name="IRC Notification" href="documentation/1_1/user_guides/notification/irc.html"/>
+            <item name="Jabber Notification" href="documentation/1_1/user_guides/notification/jabber.html"/>
+            <item name="MSN Notification" href="documentation/1_1/user_guides/notification/msn.html"/>
+            <item name="Wagon Notification" href="documentation/1_1/user_guides/notification/wagon.html"/>
             <!-- item name="mail to an address, mail to latest committers, irc, jabber, msn, wagon, alwaysSend..."/ -->
         </item>
-        <item name="Building a project">
+        <item name="Building a project" href="documentation/1_1/user_guides/building_project/index.html" collapse="true">
             <item name="Scheduled Build"/>
-            <item name="Forced Build/>
+            <item name="Forced Build"/>
         </item>
-        <item name="Release Management"/>
+        <item name="Release Management" href="documentation/1_1/user_guides/release/index.html"/>
       </item>
       <item name="Knowledge Base" href="documentation/1_1/knowledge_base/index.html" collapse="true">
         <item name="FAQs" href="documentation/1_1/knowledge_base/faqs.html"/>
       </item>
-      <item name="Administrator's Guides" collapse="true">
-        <item name="Managing Users and Security">
-            <item name="LDAP Configuration"/>
+      <item name="Administrator's Guides" href="documentation/1_1/administrator_guides/index.html" collapse="true">
+        <item name="Managing Users and Security" href="documentation/1_1/administrator_guides/security/index.html" collapse="true">
+            <item name="LDAP Configuration" href="documentation/1_1/administrator_guides/security/ldap.html"/>
         </item>
-        <item name="Adding Project Group"/>
-        <item name="Managing Builders"/>
-        <item name="Managing JDKs"/>
-        <item name="Managing Profiles"/>
-        <item name="Managing Schedules"/>
-        <item name="Managing General Configuration (configuration and appearance)"/>
+        <item name="Adding Project Group" href="documentation/1_1/administrator_guides/projectgroup.html"/>
+        <item name="Managing Builders" href="documentation/1_1/administrator_guides/builder.html"/>
+        <item name="Managing JDKs" href="documentation/1_1/administrator_guides/jdk.html"/>
+        <item name="Managing Profiles" href="documentation/1_1/administrator_guides/profiles.html"/>
+        <item name="Managing Schedules" href="documentation/1_1/administrator_guides/schedules.html"/>
+        <item name="Managing General Configuration" href="documentation/1_1/administrator_guides/configuration.html"/> <!-- (configuration and appearance) -->
       </item>
-      <item name="Developer's Guides" collapse="true">
-        <item name="SVN repository structure"/>
-        <item name="XML-RPC"/>
+      <item name="Developer's Guides" href="documentation/1_1/developer_guides/index.html" collapse="true">
+        <item name="SVN repository structure" href="documentation/1_1/developer_guides/svn.html"/>
+        <item name="Building Continuum" href="documentation/1_1/developer_guides/building.html"/>
+        <!-- item name="Design" href="documentation/1_1/developer_guides/design.html"/ -->
+        <item name="XML-RPC" href="documentation/1_1/developer_guides/xmlrpc.html"/>
         <!-- item name="TO BE DEFINED"/ -->
       </item>
       <item name="Old versions" collapse="true">
@@ -111,11 +113,11 @@
       </item>
     </menu>
     <menu name="Community">
-      <item name="Community Overview"/>
-      <item name="How to Contribute"/>
-      <item name="Getting Help"/>
-      <item name="Issue Tracking"/>
-      <item name="The Continuum Team"/>
+      <item name="Community Overview" href="community.html"/>
+      <item name="How to Contribute" href="guide-helping.html"/>
+      <item name="Getting Help" href="getting-help.html"/>
+      <item name="Issue Tracking" href="issue-tracking.html"/>
+      <item name="The Continuum Team" href="team-list.html"/>
     </menu>
 
     ${reports}