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 2.7 - Roadmap
Date Sun, 27 Feb 2011 11:08:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2036/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+2.7+-+Roadmap">Camel
2.7 - Roadmap</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~davsclaus">Claus
Ibsen</a>
    </h4>
        <br/>
                         <h4>Changes (2)</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" >It should be easier to mock endpoints,
replace parts of routes and whatnot. This allows you to leave your routes untouched and use
the test kit to perform unit testing your routes. Currently the easiest approach is to add
mocks into your routes which isn&#39;t desirable in some situations. Instead you should
be able to _tell_ Camel which endpoints should be mocked and what parts of the routes should
be replaced with an alternative part. This is an ongoing process which we hope to improve
in future releases as well. <br> <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*Status:
In progress* <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*Status:
Done* <br></td></tr>
            <tr><td class="diff-unchanged" > <br>h2. See Also <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="Camel2.7-Roadmap-Camel2.7roadmap"></a>Camel 2.7 roadmap</h2>

<p>This is a roadmap which details the overall and major goals for Camel 2.7. Fell free
to discuss this at the Camel <a href="/confluence/display/CAMEL/Mailing+Lists" title="Mailing
Lists">Mailing Lists</a> if you have ideas or feedback.<br/>
The goals on this page was intended to be introduced in <a href="/confluence/display/CAMEL/Camel+3.0+-+Roadmap"
title="Camel 3.0 - Roadmap">Camel 3.0</a>. After discussing this on the <a href="http://camel.465427.n5.nabble.com/DISCUSS-Dropping-support-for-java-1-5-from-camel-2-7-0-onwards-tp3354712p3354712.html"
class="external-link" rel="nofollow">Developer List</a> we decided to bring forward
some of the goals for 3.0 to 2.7. Those goals is listed on this page:</p>

<h4><a name="Camel2.7-Roadmap-JDK1.6"></a>JDK 1.6+ </h4>

<p>Camel 2.7 should bump the JDK minimum version to 1.6.<br/>
Camel 1.x - 2.6.0 supports JDK 1.5+. </p>

<p><b>Status: Done</b></p>

<h4><a name="Camel2.7-Roadmap-Spring3.x"></a>Spring 3.x</h4>

<p>Camel 2.7 should bump the minimum version of Spring to 3.0+.<br/>
Camel 1.x - 2.6.0 supports Spring 2.0+</p>

<p><b>Status: Done</b></p>

<h4><a name="Camel2.7-Roadmap-Logging"></a>Logging</h4>

<p>We should switch from <tt>commons-logging</tt> to <tt>slf4j</tt></p>

<p><b>Status: Done</b></p>

<h4><a name="Camel2.7-Roadmap-JUnit"></a>JUnit</h4>

<p>Use JUnit 4.x by default. However JUnit 4.x is backwards compatible with JUnit 3.x.
The change would be to remove the JUnit 3.x support in <tt>camel-test</tt> JAR
if that's desirable.</p>

<h4><a name="Camel2.7-Roadmap-camelosgitest"></a>camel-osgi-test</h4>

<p>When testing your Camel apps with OSGi you may use PaxExam for that. We should create
a test kit for osgi, like we have camel-test for regular junit testing. The test kit should
make it easy for end users to have their apps tested with OSGi. We already have pieces in
the <tt>tests/camel-itest-osgi</tt>. We just need to clean and shape it up so
its ready for end users as well. And of course add documentation as well.<br/>
And then we should use it in <tt>camel-itest-osgi</tt> of course.</p>

<h4><a name="Camel2.7-Roadmap-Improveunittesting"></a>Improve unit testing</h4>
<p>It should be easier to mock endpoints, replace parts of routes and whatnot. This
allows you to leave your routes untouched and use the test kit to perform unit testing your
routes. Currently the easiest approach is to add mocks into your routes which isn't desirable
in some situations. Instead you should be able to <em>tell</em> Camel which endpoints
should be mocked and what parts of the routes should be replaced with an alternative part.
This is an ongoing process which we hope to improve in future releases as well.</p>

<p><b>Status: Done</b></p>

<h2><a name="Camel2.7-Roadmap-SeeAlso"></a>See Also</h2>
<p><a href="/confluence/display/CAMEL/Camel+3.0+-+Roadmap" title="Camel 3.0 - Roadmap">Camel
3.0 &#45; Roadmap</a></p>
    </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+2.7+-+Roadmap">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=25200176&revisedVersion=4&originalVersion=3">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.7+-+Roadmap?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message