Author: buildbot
Date: Wed Apr 24 14:18:07 2013
New Revision: 859732
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 Wed Apr 24
14:18:07 2013
@@ -79,6 +79,8 @@
<p>If you are experiencing problems using Camel then please report your
problem to our <a shape="rect" href="discussion-forums.html" title="Discussion
Forums">Discussion Forums</a>. This allows the entire community to help with
your problem. If indeed a bug has been identified in the Camel software, then
document the problem in our <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a>. Please
refrain from immediately opening a ticket in the issue tracker unless you are
certain it's a problem in the Camel software. If you are in doubt, we
appreciate asking the <a shape="rect" href="discussion-forums.html"
title="Discussion Forums">Discussion Forums</a> first.</p>
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1">Please read the section below (<em>How to get help</em>), and
follow the bullets advised there first.</td></tr></table></div>
+
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Reporting bugs - Please read this first</b><br clear="none">We
prefer people to get in touch first using the mailing list or forums. Or take
time to read FAQs, or search in the mailing list archives to find answers.<br
clear="none">
Unfortunately some people create a JIRA ticket as first thing. Please don't do
that! Only if you are sure it really is a bug etc. JIRA tickets create noise<br
clear="none">
for the Camel team to react on issues that are not bugs. But already covered
in FAQs, in the mailing lists/forums etc. Or in the existing documentation.<br
clear="none">
@@ -94,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></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 discusse
d 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 use
r 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>
<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 Wed Apr 24 14:18:07 2013
@@ -79,6 +79,8 @@
<p>If you are experiencing problems using Camel then please report your
problem to our <a shape="rect" href="discussion-forums.html" title="Discussion
Forums">Discussion Forums</a>. This allows the entire community to help with
your problem. If indeed a bug has been identified in the Camel software, then
document the problem in our <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a>. Please
refrain from immediately opening a ticket in the issue tracker unless you are
certain it's a problem in the Camel software. If you are in doubt, we
appreciate asking the <a shape="rect" href="discussion-forums.html"
title="Discussion Forums">Discussion Forums</a> first.</p>
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1">Please read the section below (<em>How to get help</em>), and
follow the bullets advised there first.</td></tr></table></div>
+
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Reporting bugs - Please read this first</b><br clear="none">We
prefer people to get in touch first using the mailing list or forums. Or take
time to read FAQs, or search in the mailing list archives to find answers.<br
clear="none">
Unfortunately some people create a JIRA ticket as first thing. Please don't do
that! Only if you are sure it really is a bug etc. JIRA tickets create noise<br
clear="none">
for the Camel team to react on issues that are not bugs. But already covered
in FAQs, in the mailing lists/forums etc. Or in the existing documentation.<br
clear="none">
@@ -94,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></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 discusse
d 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 use
r 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>
<h3><a shape="rect" name="Support-Howtogethelpfaster"></a>How to get help
faster</h3>
![https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"){kind=link}