Author: buildbot
Date: Mon Dec 10 20:12:06 2012
New Revision: 841512

Log:
Staging update by buildbot for openjpa

Modified:
    websites/staging/openjpa/trunk/content/   (props changed)
    websites/staging/openjpa/trunk/content/found-a-bug.html

Propchange: websites/staging/openjpa/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 10 20:12:06 2012
@@ -1 +1 @@
-1419706
+1419716

Modified: websites/staging/openjpa/trunk/content/found-a-bug.html
==============================================================================
--- websites/staging/openjpa/trunk/content/found-a-bug.html (original)
+++ websites/staging/openjpa/trunk/content/found-a-bug.html Mon Dec 10 20:12:06 
2012
@@ -22,7 +22,7 @@ limitations under the License.
         <!-- <link href="http://openjpa.apache.org/styles/type-settings.css"; 
rel="stylesheet" type="text/css"/> -->
         <link href="./css/type-settings.css" rel="stylesheet" type="text/css"/>
         <LINK rel="schema.DC" href="http://purl.org/DC/elements/1.0/";>
-        <META name="Description" content="Apache OpenJPA -- Found a Bug
" />
+        <META name="Description" content="Apache OpenJPA -- Found a Bug" />
         <META name="Keywords" content="Apache OpenJPA, JPA, JPA 1.0, JSR-220, 
JPA2, JPA 2.0, JSR-317, " />
         <META name="Owner" content="[email protected]" />
         <META name="Robots" content="index, follow" />
@@ -68,7 +68,7 @@ limitations under the License.
                             <div class="bottom_red_bar">
                                 <div id="site-breadcrumbs">
                                     <!-- Breadcrumbs --
-                                    <a href="/">Home</a>&nbsp;&raquo&nbsp;<a 
href="/found-a-bug.html">Found a Bug
</a>
+                                    <a href="/">Home</a>&nbsp;&raquo&nbsp;<a 
href="/found-a-bug.html">Found a Bug</a>
                                      -- Breadcrumbs -->
                                 </div>
                             </div>
@@ -151,20 +151,27 @@ describing it. Please include detailed s
 <p>If you have a fix for the issue, you can generate a patch file to send the
 fix to us. You need to check out the current source code from Subversion
 (see <a href="source-code.html">Source Code</a>
-), make the necessary changes (see [Coding Standards]
-), and then do a full build with all tests enabled (see [Building]
-) and make sure the unit tests runs as expected (try {{maven clean
-install}} to run a full build), and of course, confirm that the problem is
+), make the necessary changes (see <a href="coding-standards.html">Coding 
Standards</a>
+), and then do a full build with all tests enabled (see <a 
href="building.html">Building</a>
+) and make sure the unit tests runs as expected (try to run a full build),</p>
+<div class="codehilite"><pre> <span class="n">maven</span> <span 
class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<p>and of course, confirm that the problem is
 actually fixed. Then, go to the root directory of your OpenJPA checkout,
-and run a command like {{svn diff &gt;
-OPENJPA-<JIRA_NUMBER>-<BRANCH_ID>.patch}} to generate a patch file.</p>
+and run a command like </p>
+<div class="codehilite"><pre> <span class="n">svn</span> <span 
class="n">diff</span> <span class="o">&gt;</span> <span 
class="n">OPENJPA</span><span class="o">-</span><span 
class="sr">&lt;JIRA_NUMBER&gt;</span><span class="o">-</span><span 
class="sr">&lt;BRANCH_ID&gt;</span><span class="o">.</span><span 
class="n">patch</span>
+</pre></div>
+
+
+<p>to generate a patch file.</p>
 <p>To submit a patch, create an issue in JIRA that describes the problem, add
 your patch file as an attachment (don't forget to select the "Grant license
 to ASF for inclusion in ASF works" option), and then edit the JIRA to
 select the <a 
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12313253";>Patch
 Available</a>
  check box.  Please include detailed steps to reproduce the problem in the
-issue description, and a test case in the patch where possible (see [Testing]
-).</p>
+issue description, and a test case in the patch where possible (see <a 
href="testing.html">Testing</a>).</p>
 <p>For larger contributions, like new features or more complex bug fixes, you
 should also have an <a href="http://www.apache.org/licenses/#clas";>Individual 
Contributor License Agreement</a>
  on file with the ASF.</p>


Reply via email to