Scarab commit: svn commit: r11169 - branches/20120417_mavenPort/www/book
[email protected] Tue, 17 Apr 2012 02:19:36 -0700 (PDT)
| Newsgroups | gmane.comp.java.scarab.cvs |
|---|---|
| Message-ID | <[email protected]> |
Author: mcoss Date: 2012-04-17 02:19:36-0700 New Revision: 11169 Modified: branches/20120417_mavenPort/www/book/eclipse-en.xml branches/20120417_mavenPort/www/book/ergonomy-en.xml branches/20120417_mavenPort/www/book/intro-en.xml branches/20120417_mavenPort/www/book/issues-en.xml branches/20120417_mavenPort/www/book/scarab-admin-en.xml branches/20120417_mavenPort/www/book/scarab-dev-en.xml branches/20120417_mavenPort/www/book/scarab-user-en.xml branches/20120417_mavenPort/www/book/workflow1-en.xml branches/20120417_mavenPort/www/book/workflow2-en.xml branches/20120417_mavenPort/www/book/xml-rpc-en.xml Log: FIX - Replaced special characters in docbook files by their real characters as replacements are not supported by com.agilejava.docbkx.docbkx-maven-plugin. Modified: branches/20120417_mavenPort/www/book/eclipse-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/eclipse-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/eclipse-en.xml (original) +++ branches/20120417_mavenPort/www/book/eclipse-en.xml 2012-04-17 02:19:36-0700 @@ -5,23 +5,23 @@ <sect2> <title>Getting the subclipse plugin</title> <simpara>You will need the Subclipse plugin to connect to the Subversion repository that hosts and manages the Scarab source code base.</simpara> - <simpara>If you do not have this plugin already installed, you will find detailed installation instructions at this URL : + <simpara>If you do not have this plugin already installed, you will find detailed installation instructions at this URL: <ulink url="http://subclipse.tigris.org/install.html">http://subclipse.tigris.org/install.html</ulink> </simpara> </sect2> <sect2> <title>Connecting to the Scarab Subversion repository</title> - <para>Select the 'SVN Repository Exploring' perspective :</para> + <para>Select the 'SVN Repository Exploring' perspective:</para> <screenshot> <graphic fileref="images/svn03.png"/> </screenshot> - <para>Right-click in the SVN Repository view to connect to a new Subversion repository :</para> + <para>Right-click in the SVN Repository view to connect to a new Subversion repository:</para> <screenshot> <graphic fileref="images/svn04.png"/> </screenshot> - <para>The connection URL is :: <emphasis>http://scarab.tigris.org/svn/scarab</emphasis> + <para>The connection URL is: <emphasis>http://scarab.tigris.org/svn/scarab</emphasis> </para> - <simpara>and the Root URL is : <emphasis>http://scarab.tigris.org/svn</emphasis> + <simpara>and the Root URL is: <emphasis>http://scarab.tigris.org/svn</emphasis> </simpara> <para>If you are a Scarab committer, use your tigris.org login and password to connect; otherwise you do not need any particular identification and you may leave the <emphasis>User</emphasis> and <emphasis>Password</emphasis> fields blank (though it seems that any <emphasis>User/Password</emphasis> will work here).</para> @@ -32,11 +32,11 @@ <screenshot> <graphic fileref="images/svn06.png"/> </screenshot> - <para>You can then use 'Checkout As Project', which allows you to rename the project (otherwise Eclipse would name it <emphasis>trunk</emphasis>, which is not that meaningful). </para> + <para>You can then use 'Checkout As Project, which allows you to rename the project (otherwise Eclipse would name it <emphasis>trunk</emphasis>, which is not that meaningful). </para> <screenshot> <graphic fileref="images/svn07.png"/> </screenshot> - <para>The 'New Project' wizard appears. Choose 'Java project'.</para> + <para>The 'New Project' wizard appears. Choose 'Java project'.</para> <screenshot> <graphic fileref="images/svn08.png"/> </screenshot> @@ -48,7 +48,7 @@ <screenshot> <graphic fileref="images/svn09b.png"/> </screenshot> - <para>Last step : it is best to change the <emphasis>Default output folder</emphasis> to :<computeroutput>scarab/target/webapps/scarab/scarab/WEB-INF/classes</computeroutput> + <para>Last step: it is best to change the <emphasis>Default output folder</emphasis> to:<computeroutput>scarab/target/webapps/scarab/scarab/WEB-INF/classes</computeroutput> </para> <screenshot> <graphic fileref="images/svn10.png"/> @@ -65,7 +65,7 @@ </sect2> <sect2> <title>Generating the required files with Maven</title> - <simpara>At the root of your project, type the following commands :</simpara> + <simpara>At the root of your project, type the following commands:</simpara> <simpara> <computeroutput>maven war:inplace</computeroutput> </simpara> @@ -91,7 +91,7 @@ <simpara>Select the 4.0.x version</simpara> </listitem> <listitem> - <simpara>Tomcat directory : the <computeroutput>tomcat</computeroutput> directory in your Scarab project</simpara> + <simpara>Tomcat directory: the <computeroutput>tomcat</computeroutput> directory in your Scarab project</simpara> </listitem> <listitem> <simpara>Context declaration in server.xml</simpara> @@ -100,7 +100,7 @@ </sect3> <sect3> <title>Setting the project Tomcat properties</title> - <simpara>In Project | Properties | Tomcat :</simpara> + <simpara>In Project | Properties | Tomcat:</simpara> <screenshot> <graphic fileref="images/sysdeo1.png"/> </screenshot> Modified: branches/20120417_mavenPort/www/book/ergonomy-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/ergonomy-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/ergonomy-en.xml (original) +++ branches/20120417_mavenPort/www/book/ergonomy-en.xml 2012-04-17 02:19:36-0700 @@ -3,27 +3,27 @@ <sect1> <title>Scarab navigation</title> <para>The Scarabinterface is organized to allow access to all major functionality from anywhere in the application. Each of the action screens provides relevant information along with links to access further details as needed. A unified and consistent interface allows you to easily recognize the types of information and actions available on each screen.</para> - <para>Each screen provides the following navigational aids :</para> + <para>Each screen provides the following navigational aids:</para> <itemizedlist> <listitem> <para> - <emphasis role="bold">The Left navigation bar :</emphasis> The navigation bar is organized by issue type, then by function. To access functionality within a specific issue type, select the title of the issue type on the left navigation bar. The functionality available to that issue type will appear below the title.</para> + <emphasis role="bold">The Left navigation bar:</emphasis> The navigation bar is organized by issue type, then by function. To access functionality within a specific issue type, select the title of the issue type on the left navigation bar. The functionality available to that issue type will appear below the title.</para> </listitem> <listitem> <para> - <emphasis role="bold">The Query bar :</emphasis> The query bar provides access to the search tools. The issue ID box allows you to access a specific issue number. The select query box provides access to the Advanced and Custom query features. If you have any saved queries, they will appear in the select query box.</para> + <emphasis role="bold">The Query bar:</emphasis> The query bar provides access to the search tools. The issue ID box allows you to access a specific issue number. The select query box provides access to the Advanced and Custom query features. If you have any saved queries, they will appear in the select query box.</para> </listitem> <listitem> <para> - <emphasis role="bold">Section titles :</emphasis> Most information screens are organized in tabular format. Each section is presented with an informative section header, describing the section and, often, providing general information about the section. Column headers with arrows can be used to change the sort order for that table. For the sort column, the title has an arrow indicating the direction of the sort: the default is ascending. To change the direction of the sort click on the arrow.</para> + <emphasis role="bold">Section titles:</emphasis> Most information screens are organized in tabular format. Each section is presented with an informative section header, describing the section and, often, providing general information about the section. Column headers with arrows can be used to change the sort order for that table. For the sort column, the title has an arrow indicating the direction of the sort: the default is ascending. To change the direction of the sort click on the arrow.</para> </listitem> <listitem> <para> - <emphasis role="bold">Buttons :</emphasis> Are used to indicate a set of actions that can be performed. Often you will find more than one set of buttons on a page. Buttons directly below a section will perform actions on the section only, if you have you may find an Update Optionsbutton beside an attribute selector in one section. This indicates that if you change the attribute clicking the button will change the options available to that attribute.</para> + <emphasis role="bold">Buttons:</emphasis> Are used to indicate a set of actions that can be performed. Often you will find more than one set of buttons on a page. Buttons directly below a section will perform actions on the section only, if you have you may find an Update Optionsbutton beside an attribute selector in one section. This indicates that if you change the attribute clicking the button will change the options available to that attribute.</para> </listitem> <listitem> <para> - <emphasis role="bold">Checkboxes :</emphasis> Are used to select list items for modification.</para> + <emphasis role="bold">Checkboxes:</emphasis> Are used to select list items for modification.</para> </listitem> </itemizedlist> <para>In many cases, helpful information is included directly on the screens to clarify unusual operations. Error messages are provided in line to help identify where the error occurred and specific means for remedy.</para> Modified: branches/20120417_mavenPort/www/book/intro-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/intro-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/intro-en.xml (original) +++ branches/20120417_mavenPort/www/book/intro-en.xml 2012-04-17 02:19:36-0700 @@ -3,43 +3,43 @@ <title>Introduction</title> <sect1> <!-- Source: the ##Introduction section in the online help --> - <title>What is Scarab ?</title> + <title>What is Scarab?</title> <para>Scarab is a highly configurable issue tracking tool that can be used for all types of projects: technical and non-technical alike. Because all parameters in the system are configurable, this tool meets the needs of the project as well as the individual user. Each implementation can be configured directly to the workflow processes of the project through the definition of issue types and attributes. The user interface is designed to be accessible and constant: once you become familiar with the look and feel you will find new processes quick to master.</para> - <para>Scarab provides a robust set of tools for issue management :</para> + <para>Scarab provides a robust set of tools for issue management:</para> <itemizedlist> <listitem> <para> - <emphasis role="bold">Issue entry :</emphasis> The issue entry process is designed to help users create meaningful issues and avoid duplication. Attributes are used to describe issues and to check the issue database for similar entries. If any duplicates are found, the user has the opportunity to review potential duplicates, add comments to like issues or modify their issue before committing it to the database. </para> + <emphasis role="bold">Issue entry:</emphasis> The issue entry process is designed to help users create meaningful issues and avoid duplication. Attributes are used to describe issues and to check the issue database for similar entries. If any duplicates are found, the user has the opportunity to review potential duplicates, add comments to like issues or modify their issue before committing it to the database. </para> </listitem> <listitem> <para> - <emphasis role="bold">Templates for issue entry :</emphasis> Frequently entered issue criteria can be saved in templates for speedy entry. Files can be attached to an issue, and are tracked directly with their issue. Users can add and edit comments to issues as needed. Users can access and review the complete issue history while viewing an issue. </para> + <emphasis role="bold">Templates for issue entry:</emphasis> Frequently entered issue criteria can be saved in templates for speedy entry. Files can be attached to an issue, and are tracked directly with their issue. Users can add and edit comments to issues as needed. Users can access and review the complete issue history while viewing an issue. </para> </listitem> <listitem> <para> - <emphasis role="bold">Issue query :</emphasis> Accessing issues in the database is simple using the query feature. Users can easily find, access and modify issues individually or in groups. The advanced query feature allows the user to create detailed issue searches, specifying values for multiple attributes and limiting their search to specific date or issue number ranges. The Custom Query feature allows the user to search by text string-the user can specify a set of information to compare against issues in the database. Frequently used queries can be saved and easily run.</para> + <emphasis role="bold">Issue query:</emphasis> Accessing issues in the database is simple using the query feature. Users can easily find, access and modify issues individually or in groups. The advanced query feature allows the user to create detailed issue searches, specifying values for multiple attributes and limiting their search to specific date or issue number ranges. The Custom Query feature allows the user to search by text string-the user can specify a set of information to compare against issues in the database. Frequently used queries can be saved and easily run.</para> </listitem> <listitem> <para> - <emphasis role="bold">Reports :</emphasis> The robust reports interface allows the user to create and save reports. Reports provide customizable and meaningful metrics.</para> + <emphasis role="bold">Reports:</emphasis> The robust reports interface allows the user to create and save reports. Reports provide customizable and meaningful metrics.</para> </listitem> <listitem> <para> - <emphasis role="bold">Email notifications :</emphasis> As important events occur, email is generated and sent to all parties associated with the event. Alert emails contain links to views of the event.</para> + <emphasis role="bold">Email notifications:</emphasis> As important events occur, email is generated and sent to all parties associated with the event. Alert emails contain links to views of the event.</para> </listitem> </itemizedlist> <para>Scarab is written in Java and based on web technologies. Scarab stores its informations in a database, often MySQL but other databases such as Oracle and PostgreSQL are supported.</para> <sect2> - <title>How does Scarab differ from other issue-tracking systems ?</title> + <title>How does Scarab differ from other issue-tracking systems?</title> <para>Scarab is highly customisable. Scarab has no predefined or hard-coded workflow (that would define what happens as an issue changes from the 'Open' to the 'Closed' status. There are no predefined artefact types (such as bug report, improvement, etc.) You are completely free to define your issue types the way that suits you best. Scarab may be less easy to understand and use at the beginning but you will get a tool that suits your needs better at the end.</para> <para>Most other issue tracking systems (open-source or commercial) have an issue processing logic that is embedded in the application. This means that you are often caught in the logic defined by these systems. Scarab does not limit you that way.</para> </sect2> </sect1> <sect1> <title>Scarab history</title> - <para>To stay short, let's say that Scarab was born from the passion of a highly talented developer : Jon Scott Stevens. Jon was a key figure in the Apache Jakarta project, where he played a major role in the Velocity and Turbine projects.</para> + <para>To stay short, let's say that Scarab was born from the passion of a highly talented developer: Jon Scott Stevens. Jon was a key figure in the Apache Jakarta project, where he played a major role in the Velocity and Turbine projects.</para> <para>His aim was to design and develop a compelling replacement for Bugzilla.</para> - <para>CollabNet gave him an opportunity to develop this software in open-source — but also to integrate this tool in their collaborative development suite.</para> + <para>CollabNet gave him an opportunity to develop this software in open-source, but also to integrate this tool in their collaborative development suite.</para> <para>Today, CollabNet is no longer the driving force behind the development of Scarab; they left this role to a small team of developers from around the world but continue to provide support and useful advice on certain occasions.</para> </sect1> <sect1> @@ -47,28 +47,28 @@ <title>Scarab functionality at a glance</title> <itemizedlist> <listitem> - <para>A full set of functions such as those found in other issue tracking systems : issue entry, queries, reports, event notification, collaborative accumulation of comments, dependency tracking.</para> + <para>A full set of functions such as those found in other issue tracking systems: issue entry, queries, reports, event notification, collaborative accumulation of comments, dependency tracking.</para> </listitem> <listitem> <para>On top of these standard functions, Scarab provides an unlimited number of fully configurable modules (your projects), of artefact types (Defect, Improvement request, Requirements,...), of Attributes (Operating system, Status, Priority, etc.), of Attribute options (P1, P2, P3) that can all be defined on a per-module basis, so that any module can be configured for specific needs..</para> </listitem> <listitem> - <para>Import/Export interface via XML : allows an easy migration from other tracking systems (e.g. Bugzilla).</para> + <para>Import/Export interface via XML: allows an easy migration from other tracking systems (e.g. Bugzilla).</para> </listitem> <listitem> <para>Modular code design: allows manageable modifications of existing and new features over time.</para> </listitem> <listitem> - <para>Integrated customization UI : Scarab is fully customizable through a set of administrative pages.</para> + <para>Integrated customization UI: Scarab is fully customizable through a set of administrative pages.</para> </listitem> <listitem> <para>Easily modifiable UI look and feel.</para> </listitem> <listitem> - <para>Integration :Scarab can be integrated into larger systems by re-implementing key interfaces.</para> + <para>Integration: Scarab can be integrated into larger systems by re-implementing key interfaces.</para> </listitem> <listitem> - <para>Based on application server technologies :Scarab is built using Java Servlet technology for speed, scalability, maintainability, and ease of installation.</para> + <para>Based on application server technologies, Scarab is built using Java Servlet technology for speed, scalability, maintainability, and ease of installation.</para> </listitem> </itemizedlist> </sect1> Modified: branches/20120417_mavenPort/www/book/issues-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/issues-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/issues-en.xml (original) +++ branches/20120417_mavenPort/www/book/issues-en.xml 2012-04-17 02:19:36-0700 @@ -2,23 +2,23 @@ <chapter> <!-- Source: ##UserIssues section of the online help --> <title>Entering and managing issues</title> - <para>Scarab has a very dynamic issue management strategy. Committing, tracking and modifying issues is a simple process. Scarab has the following issue management features :</para> + <para>Scarab has a very dynamic issue management strategy. Committing, tracking and modifying issues is a simple process. Scarab has the following issue management features:</para> <itemizedlist> <listitem> <para> - <emphasis role="bold">Relations :</emphasis> Scarab can track relationships between issues. Dependencies between issues can be flagged and tracked through either the issue entry process or while reviewing one or multiple issues. </para> + <emphasis role="bold">Relations:</emphasis> Scarab can track relationships between issues. Dependencies between issues can be flagged and tracked through either the issue entry process or while reviewing one or multiple issues. </para> </listitem> <listitem> <para> - <emphasis role="bold">Change tracking :</emphasis> All changes made along with information about the user who made the change, when the change was made and any comments committed along with the change are tracked with the issue.</para> + <emphasis role="bold">Change tracking:</emphasis> All changes made along with information about the user who made the change, when the change was made and any comments committed along with the change are tracked with the issue.</para> </listitem> <listitem> <para> - <emphasis role="bold">Comment viewing and editing: :</emphasis> All comments made to the issue are tracked. Comments allow support or other type conversations to be viewable and editable by any parties interested in the progress of an issue. </para> + <emphasis role="bold">Comment viewing and editing:</emphasis> All comments made to the issue are tracked. Comments allow support or other type conversations to be viewable and editable by any parties interested in the progress of an issue. </para> </listitem> <listitem> <para> - <emphasis role="bold">Save frequently entered information: :</emphasis> The issue entry template feature allows you to create a frequently used set of data points for attributes in a template. When a template is used, the issue entry form is pre-populated and the user can alter information as needed.</para> + <emphasis role="bold">Save frequently entered information:</emphasis> The issue entry template feature allows you to create a frequently used set of data points for attributes in a template. When a template is used, the issue entry form is pre-populated and the user can alter information as needed.</para> </listitem> </itemizedlist> <sect1> Modified: branches/20120417_mavenPort/www/book/scarab-admin-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/scarab-admin-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/scarab-admin-en.xml (original) +++ branches/20120417_mavenPort/www/book/scarab-admin-en.xml 2012-04-17 02:19:36-0700 @@ -9,7 +9,7 @@ <book> <bookinfo> <title>Scarab - Administration Guide</title> - <subtitle>Scarab for sysadmin's</subtitle> + <subtitle>Scarab for sysadmin's</subtitle> <corpauthor>The Scarab Development Team</corpauthor> <editor> <firstname>Jean-François</firstname> Modified: branches/20120417_mavenPort/www/book/scarab-dev-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/scarab-dev-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/scarab-dev-en.xml (original) +++ branches/20120417_mavenPort/www/book/scarab-dev-en.xml 2012-04-17 02:19:36-0700 @@ -13,7 +13,7 @@ <!-- $Id --> <book> <bookinfo> - <title>Scarab - Developer's Guide</title> + <title>Scarab - Developer's Guide</title> <subtitle>Scarab for Scarab developers</subtitle> <corpauthor>The Scarab Development Team</corpauthor> <editor> Modified: branches/20120417_mavenPort/www/book/scarab-user-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/scarab-user-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/scarab-user-en.xml (original) +++ branches/20120417_mavenPort/www/book/scarab-user-en.xml 2012-04-17 02:19:36-0700 @@ -18,7 +18,7 @@ <!-- $Id --> <book> <bookinfo> - <title>Scarab - User's Guide</title> + <title>Scarab - User's Guide</title> <subtitle>Scarab for mere mortals</subtitle> <corpauthor>The Scarab Development Team</corpauthor> <editor> Modified: branches/20120417_mavenPort/www/book/workflow1-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/workflow1-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/workflow1-en.xml (original) +++ branches/20120417_mavenPort/www/book/workflow1-en.xml 2012-04-17 02:19:36-0700 @@ -4,10 +4,10 @@ <sect1> <title>Introduction</title> <simpara>Workflow has been a widely debated concept for the life of Scarab. In the lighter part of what's been called "workflow" there is the enforcement of certain conditions on the issues, based on the value of its attributes, its so called "state", or other conditions. In a deeper understanding of the term, workflow deals with the integration between the Scarab actions and other systems/processes.</simpara> - <simpara>Scarab supports <emphasis>pluggable workflows</emphasis>. Until the milestone 19, the default workflow was not to have one. In fact there was a default workflow that did nothing and allowed all transitions. From milestone 20 upwards, the default option is to use a simple workflow called 'BasicWorkflow'; the behaviour of this workflow is explained below.</simpara> + <simpara>Scarab supports <emphasis>pluggable workflows</emphasis>. Until the milestone 19, the default workflow was not to have one. In fact there was a default workflow that did nothing and allowed all transitions. From milestone 20 upwards, the default option is to use a simple workflow called 'BasicWorkflow'; the behaviour of this workflow is explained below.</simpara> <note> <title>Changing workflow</title> - <simpara>If you want to change workflow to use another one or design your own, read the <emphasis>Workflow</emphasis> chapter in the <emphasis>Scarab Developer's Guide</emphasis>.</simpara> + <simpara>If you want to change workflow to use another one or design your own, read the <emphasis>Workflow</emphasis> chapter in the <emphasis>Scarab Developer's Guide</emphasis>.</simpara> </note> </sect1> <sect1> Modified: branches/20120417_mavenPort/www/book/workflow2-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/workflow2-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/workflow2-en.xml (original) +++ branches/20120417_mavenPort/www/book/workflow2-en.xml 2012-04-17 02:19:36-0700 @@ -2,7 +2,7 @@ <title>Workflow</title> <sect1> <title>Introduction</title> - <simpara>As has been said in the <emphasis>Workflow</emphasis> chapter of the <emphasis>Scarab User's Guide</emphasis>, Scarab has no "hard-coded" workflow. When saving issues, all state transitions are allowed and there is no interaction with any external system ever.</simpara> + <simpara>As has been said in the <emphasis>Workflow</emphasis> chapter of the <emphasis>Scarab User's Guide</emphasis>, Scarab has no "hard-coded" workflow. When saving issues, all state transitions are allowed and there is no interaction with any external system ever.</simpara> <simpara>Now let's have a look at how this is implemented.</simpara> </sect1> <sect1> @@ -25,7 +25,7 @@ </sect1> <sect1> <title>BasicWorkflow</title> - <simpara>This is the default workflow for all Scarab versions from milestone 20. The way it works from the user point of view is explained in the <emphasis>User's Guide</emphasis>.</simpara> + <simpara>This is the default workflow for all Scarab versions from milestone 20. The way it works from the user point of view is explained in the <emphasis>User's Guide</emphasis>.</simpara> <simpara>This workflow is implemented in the <computeroutput>org.tigris.scarab.workflow.CheapWorkflow</computeroutput> class (againts the odds). It implements the <emphasis>Workflow</emphasis> interface indirectly by inheriting from the default workflow, <computeroutput>DefaultWorkflow</computeroutput> probably not to redefine certain default behaviours.</simpara> </sect1> <sect1> Modified: branches/20120417_mavenPort/www/book/xml-rpc-en.xml Url: http://scarab.tigris.org/source/browse/scarab/branches/20120417_mavenPort/www/book/xml-rpc-en.xml?view=diff&pathrev=11169&r1=11168&r2=11169 ============================================================================== --- branches/20120417_mavenPort/www/book/xml-rpc-en.xml (original) +++ branches/20120417_mavenPort/www/book/xml-rpc-en.xml 2012-04-17 02:19:36-0700 @@ -5,7 +5,7 @@ <simpara>An example is supplied in the Scarab sources (under <computeroutput>src/java</computeroutput>):</simpara> <itemizedlist> <listitem> - <simpara>la classe <computeroutput>org.tigris.scarab.util.SimpleHandler.java</computeroutput> (server, in Scarab) is used by the Scarab-Subversion integration (read the corresponding chapter in the <emphasis>Scarab User's Guide</emphasis>);</simpara> + <simpara>la classe <computeroutput>org.tigris.scarab.util.SimpleHandler.java</computeroutput> (server, in Scarab) is used by the Scarab-Subversion integration (read the corresponding chapter in the <emphasis>Scarab User's Guide</emphasis>);</simpara> </listitem> <listitem> <simpara>la classe <computeroutput>org.tigris.scarab.util.SimpleHandlerClient.java</computeroutput> (client, in another application) is a simple example of using the server above.</simpara> ------------------------------------------------------ http://scarab.tigris.org/ds/viewMessage.do?dsForumId=3577&dsMessageId=2949041