Author: buildbot
Date: Sat Feb  2 00:19:35 2013
New Revision: 849001

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-30-roadmap.html

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

Modified: websites/production/camel/content/camel-30-roadmap.html
==============================================================================
--- websites/production/camel/content/camel-30-roadmap.html (original)
+++ websites/production/camel/content/camel-30-roadmap.html Sat Feb  2 00:19:35 
2013
@@ -81,22 +81,16 @@
 
 <h3><a shape="rect" 
name="Camel3.0-Roadmap-Tasksforcamel2.x%28prepare%29"></a>Tasks for camel-2.x 
(prepare)</h3>
 
-<h4><a shape="rect" 
name="Camel3.0-Roadmap-Exampletask%28champion%29"></a>Example task 
(champion)</h4>
-<h5><a shape="rect" name="Camel3.0-Roadmap-Endorsements"></a>Endorsements</h5>
-<p>+1: <a shape="rect" class="confluence-userlink" 
href="https://cwiki.apache.org/confluence/display/~muellerc";>Christian 
Mueller</a><br clear="none">
--1: <a shape="rect" class="confluence-userlink" 
href="https://cwiki.apache.org/confluence/display/~hadr...@apache.org";>Hadrian 
Zbarcea</a></p>
-
-<p>The Camel's hump is an ugly lump<br clear="none">
-Which well you may see at the Zoo;<br clear="none">
-But uglier yet is the hump we get<br clear="none">
-From having too little to do. <br clear="none">
-(References)<br clear="none">
-<a shape="rect" class="external-link" 
href="http://www.kipling.org.uk/poems_hump.htm"; 
rel="nofollow">CAMEL-9001</a></p>
+<h4><a shape="rect" 
name="Camel3.0-Roadmap-Improvethetestapifortestingcomponents%28jwcarman%29"></a>Improve
 the test api for testing components (jwcarman)</h4>
+
+<p>See <a shape="rect" class="external-link" 
href="https://issues.apache.org/jira/browse/CAMEL-6029";>CAMEL-6029</a>.</p>
+
+<p>No matter what choices and changes we make in the core, many tests in 
components will start failing. That is because virtually all unit tests in 
components test much more than the component itself, by setting up routes, etc. 
A simple thing would be do create something like xyzTestSupport (where xyz in 
{"Component", "Configuration", "Endpoint", "Producer", "Consumer", "Language", 
etc... }), that test a respective area without setting up routes and possibly 
use a minimal CamelContext (w/o component discover and/or other features). 
Moving component unit tests to such a framework is not complicated, a bit 
tedious, but hopefully we'll benefit (yet again) from community contributions 
and gain new committers in the process. This is probably the first thing that 
should be done that will allow us to be more productive with the other 
improvements. It can also be done in 2.x and won't require any incompatible 
changes.</p>
+
 
 <h3><a shape="rect" 
name="Camel3.0-Roadmap-Tasksforcamel3.0.0%28execute%29"></a>Tasks for 
camel-3.0.0 (execute)</h3>
 
-<h3><a shape="rect" 
name="Camel3.0-Roadmap-Tasksforcamel3.x%28finalize%29"></a>Tasks for camel-3.x 
(finalize)</h3>
-</div>
+<h3><a shape="rect" 
name="Camel3.0-Roadmap-Tasksforcamel3.x%28finalize%29"></a>Tasks for camel-3.x 
(finalize)</h3></div>
         </td>
         <td valign="top">
           <div class="navigation">


Reply via email to