GitHub user mcmonster opened a pull request:
https://github.com/apache/camel/pull/18
Added @PreConsumed annotation
Added @PreConsumed annotation to camel-jpa. Allows the state change caused
by the record being consumed to be available further down the route.
You can merge this pull
Hi,
I use camel for more that one year now and it is actual great for
integration questions. One thing that I always mess around with is
calling external web services (soap in general). And IMHO this is a
central use case for soa / integration purposes. I received the
impression that this cen
+1 for moving to git.
For the svn maven repo, I just have a quick look the artifacts, I don't think
we need them any more.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willem
Inline.
Hadrian
On 03/28/2013 09:35 AM, Daniel Kulp wrote:
On Mar 28, 2013, at 4:26 AM, Christian Müller
wrote:
Hadrian, it looks like your timing is better than my one [1] ;-)
In general, I'm +1 to switch to Git (I use git-svn at Camel since I can
remember...).
It's not clear for me righ
On Mar 28, 2013, at 4:26 AM, Christian Müller
wrote:
> Hadrian, it looks like your timing is better than my one [1] ;-)
>
> In general, I'm +1 to switch to Git (I use git-svn at Camel since I can
> remember...).
>
> It's not clear for me right now what we have to do with the projects which
>
Ok, I'm on IRC now...
Christian
On Thu, Mar 28, 2013 at 2:09 PM, Hadrian Zbarcea wrote:
> Ok, I'll run tests today as well, and when the trunk is ready we'll
> coordinate. It would be good for you to jump on irc now and then :)
>
> Hadrian
>
>
>
> On 03/28/2013 08:47 AM, Christian Müller wrote:
Ok, I'll run tests today as well, and when the trunk is ready we'll
coordinate. It would be good for you to jump on irc now and then :)
Hadrian
On 03/28/2013 08:47 AM, Christian Müller wrote:
It depends when the last outstanding issues are fixed. If they are not
fixed today, my next time slot
It depends when the last outstanding issues are fixed. If they are not
fixed today, my next time slot is Monday.
It's fine for me if you or some one else do the release.
In the meantime I do a "dry run" and fix some issues...
Best,
Christian
On Thu, Mar 28, 2013 at 1:18 PM, Hadrian Zbarcea wrot
Christian, do you want to build this release or you want me to do it?
I'd also suggest doing a full build/test before the dryRun.
Hadrian
On 03/28/2013 05:22 AM, Christian Müller wrote:
Ok, I fixed [1] and removed it from the official Apache Camel SVN and
update the docs. I will commit it int
On Thu, Mar 28, 2013 at 10:22 AM, Christian Müller
wrote:
> Ok, I fixed [1] and removed it from the official Apache Camel SVN and
> update the docs. I will commit it into Camel Extra and add the docs there
> in a few minutes/hours.
>
> We only have two outstanding issues [2].
>
> I will run a "mvn
sounds good
On 27 Mar 2013, at 20:01, Hadrian Zbarcea wrote:
> Would that something that sounds appealing to most? I think most of us
> already use mostly git anyway. The ASF infra now offers the choice.
>
> Same question goes about camel-extra, I opened an issue there [1] and as much
> as I
Ok, I fixed [1] and removed it from the official Apache Camel SVN and
update the docs. I will commit it into Camel Extra and add the docs there
in a few minutes/hours.
We only have two outstanding issues [2].
I will run a "mvn release:prepare -DdryRun=true" to check whether I hit
some issues.
Do
Hadrian, it looks like your timing is better than my one [1] ;-)
In general, I'm +1 to switch to Git (I use git-svn at Camel since I can
remember...).
It's not clear for me right now what we have to do with the projects which
are not located under trunk [2] - [6]. I don't think we need all of the
13 matches
Mail list logo
