One naming convention I really like from the Google Collections
library is using the plural name of a type/interface/base class as the
helper class for static helper methods.
So we could rename things like ExchangeHelper to Exchanges,
CamelContextHelper to CamelContexts. Much neater IMHO.
These
+1
I think the merges back to the camel-1.x are a nuisance we can live
with and will almost disappear after the fist hump.
Hadrian
On Feb 18, 2009, at 8:37 AM, James Strachan wrote:
2009/2/18 Claus Ibsen claus.ib...@gmail.com:
On Wed, Feb 18, 2009 at 1:49 PM, James Strachan
+1
On Wed, Feb 18, 2009 at 10:58 AM, Hadrian Zbarcea hzbar...@gmail.comwrote:
+1
I think the merges back to the camel-1.x are a nuisance we can live with
and will almost disappear after the fist hump.
Hadrian
On Feb 18, 2009, at 8:37 AM, James Strachan wrote:
2009/2/18 Claus Ibsen
+1
On Wed, Feb 18, 2009 at 3:33 PM, Jon Anstey jans...@gmail.com wrote:
+1
On Wed, Feb 18, 2009 at 10:58 AM, Hadrian Zbarcea hzbar...@gmail.comwrote:
+1
I think the merges back to the camel-1.x are a nuisance we can live with
and will almost disappear after the fist hump.
Hadrian
On
+1
Let's get it out in 2.0.
Willem
James Strachan wrote:
2009/2/18 Claus Ibsen claus.ib...@gmail.com:
On Wed, Feb 18, 2009 at 1:49 PM, James Strachan
james.strac...@gmail.com wrote:
One naming convention I really like from the Google Collections
library is using the plural name of a
We could always wait until 2.0 is almost ready to rock and roll to
minimise backport pain?
2009/2/18 Willem Jiang willem.ji...@gmail.com:
+1
Let's get it out in 2.0.
Willem
James Strachan wrote:
2009/2/18 Claus Ibsen claus.ib...@gmail.com:
On Wed, Feb 18, 2009 at 1:49 PM, James Strachan
+1
On Wed, Feb 18, 2009 at 9:48 AM, James Strachan
james.strac...@gmail.com wrote:
We could always wait until 2.0 is almost ready to rock and roll to
minimise backport pain?
2009/2/18 Willem Jiang willem.ji...@gmail.com:
+1
Let's get it out in 2.0.
Willem
James Strachan wrote:
