tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r980928 - in /websites/production/tapestry/content: building-tapestry-from-source.html cache/main.pageCache
Date Mon, 22 Feb 2016 03:20:40 GMT
Author: buildbot
Date: Mon Feb 22 03:20:40 2016
New Revision: 980928

Log:
Production update by buildbot for tapestry

Modified:
    websites/production/tapestry/content/building-tapestry-from-source.html
    websites/production/tapestry/content/cache/main.pageCache

Modified: websites/production/tapestry/content/building-tapestry-from-source.html
==============================================================================
--- websites/production/tapestry/content/building-tapestry-from-source.html (original)
+++ websites/production/tapestry/content/building-tapestry-from-source.html Mon Feb 22 03:20:40
2016
@@ -78,12 +78,12 @@
 </div></div><h3 id="BuildingTapestryfromSource-ProducingPatches">Producing
Patches</h3><p>If you aren't an official committer (with write access to the Apache
Tapestry Git repo), you'll need to submit changes via a patch.<br clear="none"> See
the recommendations at <a  class="external-link" href="http://commons.apache.org/patches.html">http://commons.apache.org/patches.html</a>.
(Obviously that isn't specifically for the Tapestry project, but most of the same principles
apply.)</p><p>You can use the git format-patch command to produce a nice set of
patches to attach to the relevant issue in JIRA:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">git
format-patch origin/master
 </pre>
-</div></div><p>The sooner you share your work the better. You can repeat
the steps of this workflow as often as you like, producing more patches to be attached to
the issue tracker. Once some of your patches are accepted and applied by a committer, you
can rebase your work against the latest trunk. Alternatively, if you're asked to make some
changes, you can go back to the original Git commit and modify it until the project team accepts
your changes.</p><h3 id="BuildingTapestryfromSource-TroubleshootingHints">Troubleshooting
Hints</h3><p><strong>Problem:</strong> I can't run the build. it gives
me an error in line 91:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><p>The sooner you share your work the better. You can repeat
the steps of this workflow as often as you like, producing more patches to be attached to
the issue tracker. Once some of your patches are accepted and applied by a committer, you
can rebase your work against the latest trunk. Alternatively, if you're asked to make some
changes, you can go back to the original Git commit and modify it until the project team accepts
your changes.</p><h3 id="BuildingTapestryfromSource-TroubleshootingHints">Troubleshooting
Hints</h3><p><strong>Problem 1:</strong> I can't run the build. it
gives me an error in line 91:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">20:22:11.438
[ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
 20:22:11.439 [ERROR] [org.gradle.BuildExceptionReporter] A problem occurred evaluating root
project 'tapestry-project-trunk'.
 20:22:11.440 [ERROR] [org.gradle.BuildExceptionReporter] Cause: Cannot get property 'plus'
on null object
 </pre>
-</div></div><p><strong>Solution:</strong> Use the gradle wrapper
(./gradlew build), not plain "gradle".</p></div>
+</div></div><p><strong>Solution:</strong> Use the gradle wrapper
(./gradlew build), not plain "gradle".</p><p><strong>Problem 2</strong>:
Under Linux I get java.io.FileNotFoundException saying "Too many open files"</p><p><strong>Solution</strong>:
You may have to increase the number of files your operating system allows you to have open
at once. Try <code>ulimit -n</code> to see what the current value is, and if it
is less than 2048, increase it to 2048 by editing your <code>/etc/security/limits.conf</code>
file. See your operating system's documentation for details.</p><p>&#160;</p></div>
       </div>
 
       <div class="clearer"></div>

Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.



Mime
View raw message