> Fell free to log a JIRA and work on cleaning up this.
Consider it done :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Thanks Babak for fixing the broken builds (w/ java 6).
Hadrian
On 06/05/2013 04:14 PM, bvah...@apache.org wrote:
Updated Branches:
refs/heads/master ddb599ea4 -> 5463fb1d2
CAMEL-6428: The camel-salesforce code base should support Java 6.
Project: http://git-wip-us.apache.org/repos/asf/cam
Hi
I dont think this is on purpose. I am not aware of us using any other
means of serialization that can detect these static fields and do
their own custom marshal/unmarshal.
Also see on SO
http://stackoverflow.com/questions/4565653/java-static-transient-fields
Fell free to log a JIRA and work o
Hi,
We got almost 500 declarations of "private static final transient"
fields in Camel code base. From what I know static fields are
automatically transient, so this is a redundancy (just like, let's say
marking interface methods as public).
Is there any particular reason we define static fields
> There is a way to tell git to always to rebase when you do a git pull.
These are my ugly merge commits. Sorry for the mess. :)
I configured [1] my git with global pull rebase, so I won't bother you
with merge commits anymore.
Cheers.
[1] git config --global branch.autosetuprebase always
--
H
Hi
I think we have all done 'em since its not default out of the box.
A bunch of mine was in hawtio as I got a new computer and reinstalled
my stuff from scratch, etc.
Keep on happy hacking.
On Wed, Jun 5, 2013 at 4:07 PM, Henryk Konsek wrote:
>> There is a way to tell git to always to rebase
Hi
A good practice is to pull with rebase like
git pull --rebase
Then we avoid those ugly merge commit in the commit log.
> Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/camel
There is a way to tell git to always to rebase when you do a git pull.
Though on top of my head I do
