You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2013/01/21 23:18:43 UTC

svn commit: r847490 - in /websites/production/camel/content: cache/main.pageCache camel-30-ideas.html camel-30-roadmap.html

Author: buildbot
Date: Mon Jan 21 22:18:42 2013
New Revision: 847490

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-30-ideas.html
    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-ideas.html
==============================================================================
--- websites/production/camel/content/camel-30-ideas.html (original)
+++ websites/production/camel/content/camel-30-ideas.html Mon Jan 21 22:18:42 2013
@@ -91,7 +91,7 @@ Speak up if you want to ensure a feature
 <h3><a shape="rect" name="Camel3.0-Ideas-ClearerArchitectureofCamelCore"></a>Clearer Architecture of Camel Core</h3>
 
 <p>Goals:</p>
-<ul><li>The camel components should know as little as possible about camel core</li><li>The classes needed to setup camel should be separate from the things needed at run time</li></ul>
+<ul><li>The camel components should know as little as possible about camel core</li><li>The classes needed to setup camel should be separate from the things needed at run time</li><li>Camel Core should be tiny as possible and only contain what really is core</li></ul>
 
 
 <p>So why should this be important? Currently components depend on camel-core as a whole and there are no further rules which classes the components should use and which classes should be private to core. Even classes from the impl package are needed. So this means that any refactoring we do in camel core could affect all components. As camel is growing steadily this can become quite problematic.</p>
@@ -207,7 +207,8 @@ And then we should use it in <tt>camel-i
 
 <h4><a shape="rect" name="Camel3.0-Ideas-Fasterunittests"></a>Faster unit tests</h4>
 
-<p>Decreasing the total time for our complete build from more than 2 hours at present. This means in fact we have to decrease the time of our unit tests. At present, we have many unit test which starts Camel contexts and Camel routes to test data formats, components, endpoints, consumer ... This is not really necessary in most (or all) the cases.</p>
+<p>Decreasing the total time for our complete build from more than 2 hours at present. This means in fact we have to decrease the time of our unit tests. At present, we have many unit test which starts Camel contexts and Camel routes to test data formats, components, endpoints, consumer ... This is not really necessary in most (or all) the cases. Plain unit tests are sufficient.<br clear="none">
+For the unit tests which have to start a Camel context, we should do it once per test class if possible.</p>
 
 <h4><a shape="rect" name="Camel3.0-Ideas-OSGienhancements"></a>OSGi enhancements</h4>
 <ul><li>create a single type converter registry available as OSGi service to all bundles serving as a single registry to lookup converters or to add/remove converters from custom bundles</li></ul>

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 Mon Jan 21 22:18:42 2013
@@ -81,7 +81,11 @@
 
 <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%2Fsupporter1%2Csupporter2%2C...%29"></a>Example task (champion / supporter1, supporter2, ...)</h4>
+<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/~hadrian@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">