openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r870034 - in /websites/staging/openjpa/trunk/content: ./ building.html
Date Thu, 18 Jul 2013 21:58:24 GMT
Author: buildbot
Date: Thu Jul 18 21:58:23 2013
New Revision: 870034

Log:
Staging update by buildbot for openjpa

Modified:
    websites/staging/openjpa/trunk/content/   (props changed)
    websites/staging/openjpa/trunk/content/building.html

Propchange: websites/staging/openjpa/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 18 21:58:23 2013
@@ -1 +1 @@
-1504678
+1504680

Modified: websites/staging/openjpa/trunk/content/building.html
==============================================================================
--- websites/staging/openjpa/trunk/content/building.html (original)
+++ websites/staging/openjpa/trunk/content/building.html Thu Jul 18 21:58:23 2013
@@ -619,7 +619,7 @@ include the following:</p>
 <h2 id="common-2x-build-problems">Common 2.x Build Problems</h2>
 <p><a name="Building-CheckstyleFailure"></a></p>
 <h3 id="checkstyle-failure-due-to-systemoutprint-or-systemerrprint">Checkstyle failure
due to System.out.print or System.err.print</h3>
-<p>Changes were added to build so that you can not build with code calls System.out/err.print(ln).

+<p>Changes were added to build so that the build will fail if there are any calls to
System.out/err.print(ln). 
 This was done to force people to use the proper logging facilities. If there is an honest
reason that
 you need to have System.out/err.print in your code, you can use the following comments to
turn the 
 checkstyle scanner off, then back on again.</p>



Mime
View raw message