camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Camel > Camel 3.0 - Roadmap
Date Sat, 02 Feb 2013 00:05:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/1/_/styles/combined.css?spaceKey=CAMEL&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/CAMEL/Camel+3.0+-+Roadmap">Camel
3.0 - Roadmap</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~hadrian@apache.org">Hadrian
Zbarcea</a>
    </h4>
        <br/>
                         <h4>Changes (5)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >h3. Tasks for camel-2.x (prepare)
<br> <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">h4.
Example task (champion) <br>h5. Endorsements <br>+1: [~muellerc] <br>-1:
[~hadrian@apache.org] <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">h4.
Improve the test api for testing components (jwcarman) <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">The
Camel&#39;s hump is an ugly lump <br>Which well you may see at the Zoo; <br>But
uglier yet is the hump we get <br>From having too little to do.  <br>(References)
<br>[CAMEL-9001|http://www.kipling.org.uk/poems_hump.htm] <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">See
[CAMEL-6029|https://issues.apache.org/jira/browse/CAMEL-6029]. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">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 \{&quot;Component&quot;, &quot;Configuration&quot;, &quot;Endpoint&quot;,
&quot;Producer&quot;, &quot;Consumer&quot;, &quot;Language&quot;,
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&#39;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&#39;t require any incompatible changes.
<br> <br> <br></td></tr>
            <tr><td class="diff-unchanged" >h3. Tasks for camel-3.0.0 (execute)
<br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="Camel3.0-Roadmap-Camel3.0Roadmap"></a>Camel 3.0 Roadmap</h2>

<p>This page contains a summary of the <a href="/confluence/display/CAMEL/Camel+3.0+-+Ideas"
title="Camel 3.0 - Ideas">ideas</a> planned for the camel-3.0.0 release.</p>

<h3><a name="Camel3.0-Roadmap-Tasksforcamel2.x%28prepare%29"></a>Tasks for
camel-2.x (prepare)</h3>

<h4><a name="Camel3.0-Roadmap-Improvethetestapifortestingcomponents%28jwcarman%29"></a>Improve
the test api for testing components (jwcarman)</h4>

<p>See <a href="https://issues.apache.org/jira/browse/CAMEL-6029" class="external-link"
rel="nofollow">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 name="Camel3.0-Roadmap-Tasksforcamel3.0.0%28execute%29"></a>Tasks
for camel-3.0.0 (execute)</h3>

<h3><a name="Camel3.0-Roadmap-Tasksforcamel3.x%28finalize%29"></a>Tasks
for camel-3.x (finalize)</h3>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/CAMEL/Camel+3.0+-+Roadmap">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=30749215&revisedVersion=4&originalVersion=3">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/CAMEL/Camel+3.0+-+Roadmap?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message