Author: buildbot
Date: Tue Sep 10 18:19:19 2013
New Revision: 877936
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/how-can-i-get-help.html
websites/production/camel/content/support.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/how-can-i-get-help.html
==============================================================================
--- websites/production/camel/content/how-can-i-get-help.html (original)
+++ websites/production/camel/content/how-can-i-get-help.html Tue Sep 10
18:19:19 2013
@@ -96,7 +96,7 @@ Also on the mailing lists / forums, ther
<p>Before you report a problem, you may wish to read the <a shape="rect"
href="faq.html" title="FAQ">FAQ</a>. <br clear="none">
When you report an issue, please be sure to include as much information as
possible. The more we know, the easier it is to reach an effective solution
quickly. </p>
-<ul><li><b>what are the version numbers of involved software components?</b>
(this is very important to detail)</li><li>what platform and JDK?</li><li>any
particular container being used? and if so, what version?</li><li>stack traces
generally really help! If in doubt, include the whole thing; often exceptions
get wrapped in other exceptions and the exception right near the bottom
explains the actual error, not the first few lines at the top. It's very easy
for us to skim-read past unnecessary parts of a stack trace.</li><li>log output
can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html" title="How do I change the
logging">enabling DEBUG logging</a> can help</li><li>your code &
configuration files are often useful</li><li>did it work before? what have you
changed to break it?</li><li>try upgrading to the latest release and see if
it's fixed there</li><li>try the latest SNAPSHOT to see if it's fixed in the
pre-release</li><li>search the user forum
to see if has been discussed before</li><li>see the "known issues" section in
the release notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the issue has already been reported</li></ul>
+<ul><li><b>what are the version numbers of involved software components?</b>
(this is very important to detail)</li><li>what platform and JDK?</li><li>any
particular container being used? and if so, what version?</li><li>stack traces
generally really help! If in doubt, include the whole thing; often exceptions
get wrapped in other exceptions and the exception right near the bottom
explains the actual error, not the first few lines at the top. It's very easy
for us to skim-read past unnecessary parts of a stack trace.</li><li>log output
can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html" title="How do I change the
logging">enabling DEBUG logging</a> can help</li><li>your code &
configuration files are often useful</li><li>did it work before? what have you
changed to break it?</li><li>try upgrading to the latest release and see if
it's fixed there</li><li>try the latest SNAPSHOT to see if it's fixed in the
pre-release</li><li>search the user forum
to see if has been discussed before</li><li>see the "known issues" section in
the release notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the issue has already been reported</li><li>do <b>not</b> send private emails
to Camel <a shape="rect" href="team.html" title="Team">Team</a> members to ask
them to help you faster, or in the private only. Help on Apache Camel is
volunteer based and <b>must</b> happen in the <b>open</b> on the public <a
shape="rect" href="mailing-lists.html" title="Mailing Lists">Mailing Lists</a>
or <a shape="rect" href="discussion-forums.html" title="Discussion
Forums">Discussion Forums</a>. If you want to get help faster or in private,
then see further below.</li></ul>
<h3><a shape="rect" name="HowcanIgethelp-Howtogethelpfaster"></a>How to get
help faster</h3>
Modified: websites/production/camel/content/support.html
==============================================================================
--- websites/production/camel/content/support.html (original)
+++ websites/production/camel/content/support.html Tue Sep 10 18:19:19 2013
@@ -96,7 +96,7 @@ Also on the mailing lists / forums, ther
<p>Before you report a problem, you may wish to read the <a shape="rect"
href="faq.html" title="FAQ">FAQ</a>. <br clear="none">
When you report an issue, please be sure to include as much information as
possible. The more we know, the easier it is to reach an effective solution
quickly. </p>
-<ul><li><b>what are the version numbers of involved software components?</b>
(this is very important to detail)</li><li>what platform and JDK?</li><li>any
particular container being used? and if so, what version?</li><li>stack traces
generally really help! If in doubt, include the whole thing; often exceptions
get wrapped in other exceptions and the exception right near the bottom
explains the actual error, not the first few lines at the top. It's very easy
for us to skim-read past unnecessary parts of a stack trace.</li><li>log output
can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html" title="How do I change the
logging">enabling DEBUG logging</a> can help</li><li>your code &
configuration files are often useful</li><li>did it work before? what have you
changed to break it?</li><li>try upgrading to the latest release and see if
it's fixed there</li><li>try the latest SNAPSHOT to see if it's fixed in the
pre-release</li><li>search the user forum
to see if has been discussed before</li><li>see the "known issues" section in
the release notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the issue has already been reported</li></ul>
+<ul><li><b>what are the version numbers of involved software components?</b>
(this is very important to detail)</li><li>what platform and JDK?</li><li>any
particular container being used? and if so, what version?</li><li>stack traces
generally really help! If in doubt, include the whole thing; often exceptions
get wrapped in other exceptions and the exception right near the bottom
explains the actual error, not the first few lines at the top. It's very easy
for us to skim-read past unnecessary parts of a stack trace.</li><li>log output
can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html" title="How do I change the
logging">enabling DEBUG logging</a> can help</li><li>your code &
configuration files are often useful</li><li>did it work before? what have you
changed to break it?</li><li>try upgrading to the latest release and see if
it's fixed there</li><li>try the latest SNAPSHOT to see if it's fixed in the
pre-release</li><li>search the user forum
to see if has been discussed before</li><li>see the "known issues" section in
the release notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the issue has already been reported</li><li>do <b>not</b> send private emails
to Camel <a shape="rect" href="team.html" title="Team">Team</a> members to ask
them to help you faster, or in the private only. Help on Apache Camel is
volunteer based and <b>must</b> happen in the <b>open</b> on the public <a
shape="rect" href="mailing-lists.html" title="Mailing Lists">Mailing Lists</a>
or <a shape="rect" href="discussion-forums.html" title="Discussion
Forums">Discussion Forums</a>. If you want to get help faster or in private,
then see further below.</li></ul>
<h3><a shape="rect" name="Support-Howtogethelpfaster"></a>How to get help
faster</h3>
