<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
How to Write Documentation for JBDS and JBoss Tools
</h3>
<span style="margin-bottom: 10px;">
modified by <a href="http://community.jboss.org/people/Ochikvina">OLga Chikvina</a> in <i>JBoss Tools</i> - <a href="http://community.jboss.org/docs/DOC-14250">View the full document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p><div class="toc" style="border: 1px dashed black; padding: 10px"><ul><ul><li>
<a class="jive-link-anchor-small" href="#Places_of_main_doc_team_resources">Places of main doc team resources</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Documentation_building_procedure">Documentation building procedure</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Doc_JIRA">Doc JIRA</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#JBoss_ToolsJBDS_Demos">JBoss Tools/JBDS Demos</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#JBoss_ToolsJBDS_guides_structure">JBoss Tools/JBDS guides structure</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Project_structure_schema">Project structure schema</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Inline_graphics_scale__100">Inline graphics scale - 100%</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Doc_build_process_speed_up">Doc build process speed up</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Task_reviewing">Task reviewing</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Text_validation">Text validation</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#JBDS_team_movies_update">JBDS team movies update</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#JBDS_Inline_graphics">JBDS Inline graphics</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Task_resolving_before_a_release">Task resolving before a release</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#JIRA_issues">JIRA issues</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Para_and_programlisting">Para and programlisting</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Image_canvas_size">Image canvas size</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Docs_releasing_procedure">Docs releasing procedure</a>
</li>
<ul><li>
<a class="jive-link-anchor-small" href="#Using_diffmk_to_add_updatedadded_markers_to_TOC">Using diffmk to add updated/added markers to TOC</a>
</li>
</ul><li>
<a class="jive-link-anchor-small" href="#Nightly_docs">Nightly docs</a>
</li>
</ul></ul></div></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Places_of_main_doc_team_resources"><a class="jive-link-anchor-small" name="Places_of_main_Docteam_resources"><span style="font-size: 14pt;"><strong>Places of main doc team resources</strong></span></a></h2><p>Here is the list resources related to JBDS/Tools docs:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><ol start="1"><li>SVN - <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk">https://svn.jboss.org/repos/jbosstools/trunk</a></li></ol><ul><li>doc folder with guide/guides is placed in plugin folder e.g. <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/esb/docs" target="_blank">https://svn.jboss.org/repos/jbosstools/trunk/esb/docs</a></li><li><a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies">https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies</a> - folder with movies on Tools and JBDS</li><li><a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation">https://svn.jboss.org/repos/jbosstools/trunk/documentation</a> - folder with doc resources and several guides.</li></ul><p class="MsoPlainText" style="padding-left: 30px;">— guides folder contains guides</p><p class="MsoPlainText" style="padding-left: 30px;">— jbds-docs folder is the place to generate JBDS release docs  -jbosstool-docbook-xslt - xslt styles  -jboss-tools-docs folder is the place to generate JBDS release docs  -jboss-tools-docs-architype - architype for new guides creation  -jbosstool-jdocbook-style -css styles</p><p class="MsoPlainText" style="padding-left: 30px;">— qa folder with qa resources (qa owns it)</p><p class="MsoPlainText" style="padding-left: 30px;">— whatsnew folder with what's new pages (dev team own it)</p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">   2. Doc project page contains links to release docs, nightly docs, movies — <a class="jive-link-external-small" href="http://jboss.org/tools/docs.html">http://jboss.org/tools/docs.html</a></p><ul><li>NEWS - owned by dev team</li><li>reference guides - release guides updated by us</li><li>screen casts - movies we have made</li><li>FAQ - owned by dev team</li></ul><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">   3. Doc JIRA for both tools and jbds doc projects is on jbds project JIRA —  <a class="jive-link-external-small" href="https://jira.jboss.org/jira/browse/JBDS">https://jira.jboss.org/jira/browse/JBDS</a></p><ul><li>open components tab - here is a list of components, doc component are ones with Doc- prefix.</li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Documentation_building_procedure"><a class="jive-link-anchor-small" name="Documentation_building_procedure"><span style="font-size: 14pt;"><strong>Documentation building procedure</strong></span></a></h2><p class="MsoPlainText">Here is an article on documentation building procedure <a class="jive-link-external-small" href="http://jboss.org/community/wiki/BuildingJBossToolsDocumentaion">http://jboss.org/community/wiki/BuildingJBossToolsDocumentaion</a></p><p class="MsoPlainText">Read it and try to build the docs with different profiles from here <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation">https://svn.jboss.org/repos/jbosstools/trunk/documentation</a></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Doc_JIRA"><a class="jive-link-anchor-small" name="Doc_JIRA"><span style="font-size: 14pt;"><strong>Doc JIRA</strong></span></a></h2><p class="MsoPlainText">Here is JBDS JIRA - <a class="jive-link-external-small" href="https://jira.jboss.org/jira/browse/jbds">https://jira.jboss.org/jira/browse/jbds</a></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">On the Open Issues  tab you can see the components, the docs ones have Doc- prefix. Usually when a new guide is created I asked Max to add a component for it, as it's very convenient to use guides names as components. New doc JIRA issue usually is created basing on developers' taks, to find the tasks that affects docs use filter with "affects documentation" check-box marked.</p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">Most of the issues that affects docs can be found in JBoss Tools JIRA - <a class="jive-link-external-small" href="https://jira.jboss.org/jira/browse/JBIDE">https://jira.jboss.org/jira/browse/JBIDE</a>. When a doc task is created basing on a dev task, the tasks are linked to each other with "is related to" link.</p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="JBoss_ToolsJBDS_Demos"><a class="jive-link-anchor-small" name="JBDS_Demos"><span style="font-size: 14pt;"><strong>JBoss Tools/JBDS Demos</strong></span></a></h2><ul><li><span style="font-size: 10pt;">When making a demo, in its setting choose the necessary <strong>jboss preloaders</strong> and our standard palette and save the movie with this settings, before committing it to svn.</span></li><li><p class="MsoNormal"><span style="font-size: 10pt;">When making a demo, first of all <strong>set 0,20 sec.</strong> for all frames and then adjust the time you need for some particular frames.<br/></span></p></li><li><span style="font-size: 10pt;">When it’s necessary to draw <strong>user attention</strong> to some particular element on a frame, use red ellipse (for small elements – tabs, buttons, etc.)  or rectangle (for file lists, windows, etc.)</span></li><li><p class="MsoNormal"><span style="font-size: 10pt;">When a demo is done, watch it yourself and make sure that you have <strong>enough time to read</strong> text in hints.</span></p></li><li><span style="font-size: 10pt;">When making a demo, make sure that you chose the <strong>appropriate size for hint boxes</strong>: not lot’s of empty space should be under the text and the box should look like all other ones, undamaged, ‘cause when you try to minimize it, it could change its form unproportionally, try to avoid such an effect, minimize the box till its form (not size) remains the same.</span></li><li><p class="MsoNormal"><span style="font-size: 10pt;">When making movie, make sure your <strong>Wink uses</strong> the elements from here, copy it to you wink folders.</span></p><p class="MsoNormal"><span style="font-size: 10pt;"><a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies/common_resources">https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies/common_resources</a></span></p></li><li><span style="font-size: 10pt;">When creating a new movie please <strong>use the style features</strong> located here - <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies/common_resources">https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies/common_resources</a></span></li><li><p class="MsoNormal"><span style="font-size: 10pt;">When creating demos make sure that you use correct <strong>jboss.org styles</strong>, time capture rate is more or equal 4, and the cursor is moving smoothly on the screen</span></p></li><li><p class="MsoNormal"><span style="font-size: 10pt;">When making a demo, make sure that all application forms, hints, windows are <strong>not cut</strong> with demo frame.</span></p><p class="MsoNormal"><span style="font-size: 10pt;"><span style="font-size: 10pt;">e.g. the hint is cut</span><br/></span></p></li></ul><p><span style="font-size: 14pt;">        </span> <a href="http://community.jboss.org/servlet/JiveServlet/showImage/102-14255-3-1596/image002.jpg"><span> http://community.jboss.org/servlet/JiveServlet/downloadImage/102-14255-3-1596/image002.jpg </span></a></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="JBoss_ToolsJBDS_guides_structure"><a class="jive-link-anchor-small" name="JBDS_guides_structure"><span style="font-size: 14pt;"><strong>JBoss Tools/JBDS guides structure</strong></span></a></h2><p>While creating a new or updating already existed JBoss Tools/JBDS guide, please keep to the following structure (JBoss Portlet Tools User Guide structure as an example):</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>1. Introduction<br/>    1.1. What is JBoss Portal and Portlet Tools?<br/>    1.2. Key Features of JBoss Portlet Tools<br/>    1.3. Requirements and Installation<br/>2. JBoss Portlet Tools Tasks<br/>    2.1. Creating and Deploying a Java Portlet<br/>        2.1.1. Creating a Web Project with JBoss Portlet Capabilities<br/>        2.1.2. Adding a Java Portlet to a Web Project<br/>        2.1.3. Deploying a Portlet to JBoss Portal<br/>    2.2. Creating and Deploying a JSF Portlet<br/>        2.2.1. Creating a JSF Project with JSF Portlet Capabilities<br/>        2.2.2. Adding a JSF Protlet to the Project and Deploying It to JBoss Portal<br/>    2.3. Creating and Deploying a Seam Portlet<br/>        2.3.1. Creating a Seam Project with Seam Portlet Capabilities<br/>        2.3.2. Adding a Seam Protlet to the Project and Deploying It to JBoss Portal</p><p>3. Reference<br/>        3.1. JBoss Portlet Descriptors<br/>        3.2. Wizards<br/>            3.2.1. Java Portlet Wizard<br/>            3.2.2. JSF/Seam Portlet Wizard<br/>        3.3. JBoss Portlet Preferences<br/>4. Summary<br/>    4.1. Other Relevant Resources on the Topic</p><p><strong><br/></strong></p><p><strong>Comments:</strong></p><ul><li>The "Key Features of [plugin name]" section should contain the table included key features (wizards, editors, tasks, etc.) of the plugin you're describing with short descriptions and references to the appropriate guide section.</li><li>The "Requirements and Installation" section should provide minimal requirements on the environment the plugin needs and installation procedure (or reference to it).</li><li>All procedural operations must be put into the "[plugin name] Tasks" chapter.  Each section of the chapter is a tutorial on a particular topic.</li><li>The referential data should be stored in the "Reference" chapter.</li><li>Remember to summarize the results and provide the links to other relevent resources in the "Summary" chapter.</li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Project_structure_schema"><a class="jive-link-anchor-small" name="Project_structure_schema"><span style="font-size: 14pt;"><strong>Project structure schema</strong></span></a></h2><p class="MsoPlainText"><span style="font-family: Arial,sans-serif; font-size: 10pt;">In case you need to show some project structure in the documentation you should use the "tree" utility that builds in terminal the project structure that you can copy/paste to your docs. Quite likely that the "tree" utility is not installed on your local machine, the <span style="font-family: &quot;Courier New&quot;, Courier;">sudo apt-get install tree</span> command will install this utility. You need to create the project structure schema in Linux since the <span style="font-family: &quot;Courier New&quot;, Courier;">tree</span> command in Windows draws a tree that is not as nice as the one in Linux, besides Linux is our primary OS.</span> However if you still need to draw a tree in Windows please use the <span style="font-family: &quot;Courier New&quot;, Courier;">tree /a /f</span> command. <span style="font-family: Arial,sans-serif; font-size: 10pt;">This is what the project structure should be like.</span></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">|-- pom.xml</p><p class="MsoPlainText">`-- src</p><p class="MsoPlainText">    |-- main</p><p class="MsoPlainText">    |   |-- java</p><p class="MsoPlainText">    |   |   `-- org</p><p class="MsoPlainText">    |   |       `-- docs</p><p class="MsoPlainText">    |   |           `-- richfaces</p><p class="MsoPlainText">    |   |               `-- Bean.java</p><p class="MsoPlainText">    |   |-- resources</p><p class="MsoPlainText">    |   `-- webapp</p><p class="MsoPlainText">    |       |-- WEB-INF</p><p class="MsoPlainText">    |       |   |-- faces-config.xml</p><p class="MsoPlainText">    |       |   `-- web.xml</p><p class="MsoPlainText">    |       |-- index.jsp</p><p class="MsoPlainText">    |       `-- pages</p><p class="MsoPlainText">    |           |-- index.jsp</p><p class="MsoPlainText">    |           `-- index.xhtml</p><p class="MsoPlainText">    `-- test</p><p class="MsoPlainText">        `-- java</p><p class="MsoPlainText">            `-- org</p><p class="MsoPlainText">                `-- docs</p><p class="MsoPlainText">                    `-- richfaces</p><p class="MsoPlainText">                        `-- BeanTest.java</p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Inline_graphics_scale__100"><a class="jive-link-anchor-small" name="Inline_graphics_scale"><span style="font-size: 14pt;"><strong>Inline graphics scale - 100%</strong></span></a></h2><p class="MsoPlainText">When inserting an inline graphics element please leave it unscaled. If  you   scale a tiny inline element, the image will be broken and hardly  readable.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Doc_build_process_speed_up"><a class="jive-link-anchor-small" name="Doc_build_process_speed_up"><span style="font-size: 14pt;"><strong>Doc build process speed up</strong></span></a></h2><p class="MsoPlainText">Command line option for only creating part of the outputs to speed up roundtrip.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>See the issue for details <a class="jive-link-external-small" href="https://jira.jboss.org/jira/browse/MPJDOCBOOK-7" target="_blank">https://jira.jboss.org/jira/browse/MPJDOCBOOK-7</a></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Task_reviewing"><a class="jive-link-anchor-small" name="Task_reviewing"><span style="font-size: 14pt;"><strong>Task reviewing</strong></span></a></h2><p class="MsoPlainText">When writing some article or component description or complicated section/chapter and need some review of it, let me know plz, and I’ll try to find a reviewer for your task.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Text_validation"><a class="jive-link-anchor-small" name="Text_validation"><span style="font-size: 14pt;"><strong>Text validation</strong></span></a></h2><p class="MsoPlainText">E.g.  letter “p” inside two opening tags (<section>p <title>… ) makes  the document invalid and failes <span style="font-size: 10pt;">the build on this place. Do not forget to validate xmls each time you make changes.</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="JBDS_team_movies_update"><a class="jive-link-anchor-small" name="JBDS_team_movies_update"><span style="font-size: 14pt;"><strong><strong>JBDS team movies update</strong></strong></span></a></h2><p class="MsoPlainText">When updating the guides according to some dev issue, remember about our movies collection, it also should be updated.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="JBDS_Inline_graphics"><a class="jive-link-anchor-small" name="Inline_graphics"><span style="font-size: 14pt;"><strong>JBDS Inline graphics</strong></span></a></h2><p>Documenting  UI, from time to time you talk about icons, mouse arrows that change depending on the user behavior etc. In these cases you can insert an image of the element into the documentation right into the text. DocBook allows you to embed inline graphics using:</p><p class="MsoNormal" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span style="color: black; font-size: 12pt;">      </span> <span style="color: #000096; font-size: 12pt;"><inlinemediaobject></span><span style="color: black; font-size: 12pt;"> </span></p><p><span style="color: black; font-size: 12pt;">           </span> <span style="color: #000096; font-size: 12pt;"><imageobject></span><span style="color: black; font-size: 12pt;"><br/>               </span> <span style="color: #000096; font-size: 12pt;"><imagedata</span> <span style="color: #f5844c; font-size: 12pt;">fileref</span><span style="color: #ff8040; font-size: 12pt;">=</span><span style="color: #993300; font-size: 12pt;">"images/image1.png"</span><span style="color: #000096; font-size: 12pt;">/></span><span style="color: black; font-size: 12pt;"><br/>           </span> <span style="color: #000096; font-size: 12pt;"></imageobject></span><span style="color: black; font-size: 12pt;"><br/>        </span> <span style="color: #000096; font-size: 12pt;"></inlinemediaobject></span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Task_resolving_before_a_release"><a class="jive-link-anchor-small" name="Task_resolving_before_release"><span style="font-size: 14pt;"><strong>Task resolving before a release</strong></span></a></h2><p><a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/pom.xml">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/pom.xml</a></p><p class="MsoPlainText">When you’re resolving a task, make sure that the person who will be closing the task, has enough time for its verification.</p><p class="MsoPlainText">E.g. if you resolve the task in a release day it means that QA or a person who needs to verify the task, has no time for it, and also you won’t have time to fix the task if it’s reopened.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="JIRA_issues"><a class="jive-link-anchor-small" name="JIRA_issues"><span style="font-size: 14pt;"><strong>JIRA issues</strong></span></a></h2><p class="MsoPlainText"><strong>JIRA issues format.</strong></p><p class="MsoPlainText">All your tasks in JIRA should have versions and components defined.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><strong>JIRA issues resolution.</strong></p><p class="MsoPlainText">When closing an issue, plz write some resolution as the last comment about what exactly was done.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><strong>"Fix version" of a jira issue.</strong></p><p class="MsoPlainText">When closing or resolving a jira issue, make sure “fix version” is the correct one, it must correspond to the next release version, which could be found on project jira page on Version tab.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Para_and_programlisting"><a class="jive-link-anchor-small" name="Para_and_programlisting"><span style="font-size: 14pt;"><strong>Para and programlisting</strong></span></a></h2><p class="MsoPlainText">Don’t insert programlisting into para tags, it causes damaged code on a page.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h2 id="Image_canvas_size"><a class="jive-link-anchor-small" name="Image_canvas_size"><span style="font-size: 14pt;"><strong>Image canvas size</strong></span></a></h2><p class="MsoPlainText">When print-screening an image, please make sure that canvas size (uninformative white space around) of it is not to large, if yes, trim it.</p><h2 id="Docs_releasing_procedure"><a class="jive-link-anchor-small" name="Image_canvas_size"><span style="font-size: 14pt;"><strong>Docs</strong></span> <span style="font-size: 14pt;">releasing procedure</span></a></h2><p class="MsoPlainText">The first step you have to do is to generate new master_output.xml files for all the guides that will be included into the bundle.</p><h3 id="Using_diffmk_to_add_updatedadded_markers_to_TOC"><a class="jive-link-anchor-small" name="Using_Diffmk"><span style="font-size: 14pt;"><strong style="font-size: 12pt; ">Using diffmk to add updated/added markers to TOC</strong></span></a></h3><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">This procedure is required because it is necessary to compare documentation of the previous release version with the current one and add update/added markers to TOC, we use DiffMk version 3.0.a1. tool.</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">We added two script files in the</span> <span style="font-family: courier new,courier; font-size: 10pt;">bin</span> <span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">folder of the DiffMk distribution:</span></p><ul><li>run.sh</li><li>run_mkdiff.sh.</li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">The first is responsible for comparing 2 files and producing a third file with *diff* markers. The second one we use to indicate the files to compare and the output files, the format is the following: ./run.sh [<em>the path to the file</em>] [<em>the path to the file modified</em>] [<em>the path to the output file</em>]</span></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">To identify the changes between two different revisions of the same guide, use the following line:</span> <span style="font-family: courier new,courier;">./run.sh /path/to/the/old/revision/guide/master.xml /path/to/the/current/revision/guide/master.xml /path/to/the/produced/by/diffmk/master_output.xml</span></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">Next, run the</span> <span style="font-family: courier new,courier;">run_mkdiff.sh</span></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">Actually, the DiffMk is not an ideal tool for comparing. It has a lot of lacks. Here are some of such lacks we run into:</span></p><ul><li>It removes the HTML entities when outputs the file, for instance &amp; in the links;</li><li>Sometimes it mixes the structure of the document, for instance, put the <chapter> into the <chapter>;</li><li>Sometimes it deletes the tags such as <imageobject>.</li></ul><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">Thus, in order to build the docs with diff markers, the next step is validating and checking the <span style="font-family: courier new,courier;">master_output.xml</span> files carefully.</span></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">When the check and </span><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">validation</span><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"> is done the next step you have to do is to build documentation bundle with updated/new markers on the TOC and required styles.</span></p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">Here we have to admit that doc bundels for JBDS and JBT releases differ from each other.JBDS documentation has "com"(red styles), while JBT docs are built in blue ones("org" styles).If you need  JBDS doc release bundle,please, use "releaseJBDS" profile,othervise <span lang="EN"> </span></span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><span lang="EN"> </span></span> </p><p>"release" profile meets your needs.</p><p>You can build release guides one by one using</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-size: 10pt; font-family: courier new,courier; ">mvn clean install -P releaseJBDS</span></p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">or</span></p><p class="MsoPlainText"><span style="font-size: 10pt; font-family: courier new,courier; ">mvn clean install -P release</span></p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">maven command and then collect all the docs together.</span></p><p class="MsoPlainText" style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText"><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">But the least time-consuming method is to build the whole bundle from <em>jbosstools_trunk\documentation\jboss-tools-docs</em>  directory using</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span style="font-size: 10pt; font-family: courier new,courier; ">mvn assembly:assembly -P releaseJBDS</span></p><p><span style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">or</span></p><p><span style="font-size: 10pt; font-family: courier new,courier; ">mvn assembly:assembly -P release</span></p><p><span style="font-size: 10pt; font-family: courier new,courier; "> <span style="font-family: arial,helvetica,sans-serif;">maven command.After it </span></span><span style="font-size: 10pt; font-family: arial,helvetica,sans-serif; ">all the guides </span><span style="font-size: 10pt; font-family: courier new,courier; "><span style="font-family: arial,helvetica,sans-serif;">will be built and collected in </span><em>en/</em> <span style="font-family: arial,helvetica,sans-serif;">folder.</span></span></p><p><span style="font-size: 10pt; font-family: courier new,courier; "><br/></span></p><p style="padding-left: 30px;"><span style="font-size: 10pt; font-family: courier new,courier; "><em>Note,that <strong>eclipse</strong> guides' versions should be excluded from the final version of the bundle.</em><br/></span></p><p><span style="font-size: 10pt;"><br/></span></p><p><span style="font-size: 12pt; font-family: times new roman,times; ">I<span style="font-size: 10pt; font-family: arial,helvetica,sans-serif; ">n the end the created release bundle should be uploaded to the site.</span></span></p><p><span style="font-size: 10pt; font-family: courier new,courier; "><span style="font-size: 10pt; font-family: arial,helvetica,sans-serif; ">JBDS release documentation should be placed here:</span><a class="jive-link-external-small" href="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/">http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/</a></span></p><p><span style=": ; font-size: 10pt; font-family: courier new,courier; "><span style="font-family: arial,helvetica,sans-serif;">while JBT release documentation should be here:</span> <a class="jive-link-external-small" href="http://docs.jboss.org/tools/">http://docs.jboss.org/tools/</a>.</span></p><p><span style=": ; font-size: 10pt; font-family: courier new,courier; "><br/></span></p><h2 id="Nightly_docs"><a class="jive-link-anchor-small" name="Nightly_docs"><span style="font-size: 14pt;"><strong>Nightly docs</strong></span></a></h2><p class="MsoPlainText">Nightly docs online:</p><p class="MsoPlainText"><a class="jive-link-external-small" href="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs/</a></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">Here is svn for it:</p><p class="MsoPlainText"><a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs</a></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">Here is Hudson for it:</p><p class="MsoPlainText"><a class="jive-link-external-small" href="http://hudson.qa.jboss.com/hudson/job/jbosstools-docs-nightly/">http://hudson.qa.jboss.com/hudson/job/jbosstools-docs-nightly/</a> (to build nightly docs VPN access and admin pass are required)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">When a new guide is created it should be added to nightly docs build</p><ul><li>add it to pom.xml: <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/pom.xml">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/pom.xml</a></li></ul><p><a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/pom.xml">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/pom.xml</a></p><ul><li><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">add it to all-guides.xml:</span> <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/all-guides.xml">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/all-guides.xml</a></li><li>add it to the index.html (master.xml) page: <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/index/en/master.xml">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs/index/en/master.xml</a></li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">See that the guide is added and email Denis Golovin asking to add a new guide to the server settings for nightly docs.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p class="MsoPlainText">Build the guides with <span style="font-family: courier new,courier;">mvn clean install</span> from <a class="jive-link-external-small" href="https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs">https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs</a></p><div id="_mcePaste" style="overflow: hidden; position: absolute; width: 1px; height: 1px; top: 0px; left: -10000px;"><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><a class="jive-link-wiki-small" href="http://community.jboss.org/docs/DOC-14252">Places of main Docteam resources</a></div></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Comment by <a href="http://community.jboss.org/docs/DOC-14250">going to Community</a></p>
<p style="margin: 0;">Create a new document in JBoss Tools at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2128">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>