If I recall correctly the need for a more specialized mllp functionality
with camel-hl7 was pointed out a few times in the past years in camel.
There was even a contribution [1] that for some reason was not included.
From my direct interaction with the healthcare industry, camel is
heavily use
Done. You can try it now. Thanks for the contributions.
Hadrian
On 11/24/2014 04:44 AM, Ruurtjan Pul wrote:
Hi dev team,
Could you give me write-access on the Camel wiki? I've spotted some minor
flaws I'd like to fix.
I've sent a signed ICLA to Apache (see email below) and I've created an
acco
Done.
Jyrki, please let me know if it doesn't work. Christian, enjoy the vacation.
Cheers,
Hadrian
On 11/22/2014 04:51 PM, Christian Müller wrote:
I'm in vacation without access to a PC/Mac. Could one of the other PMC
please grant the karma.
Best,
Christian
Am 21.11.2014 09:10 schrieb "Jyrki
Christian, I'll be a standby second if for whatever reason you won't be
able to make it.
Thanks,
Hadrian
On 10/14/2014 03:39 PM, Christian Müller wrote:
I could do the 2.12.5 release (last planned patch release of the 2.12.x
branch).
If nobody has an important ticket which should be included,
+1.
That's pretty much what we always did. I think it warrants more an
announcement than a discussion.
Cheers,
Hadrian
On 10/01/2014 02:44 AM, Claus Ibsen wrote:
Hi
Now that we have 2.14.0 out of the door, I think its time we do a
round of patch releases.
Camel 2.12.5 would be the last pl
+1
Too late to count, but builds from sources produce the expected results
with both Java 6 and Java 7. Signatures are good, features work,
examples work.
Hadrian
On 02/25/2014 12:44 AM, Willem Jiang wrote:
The vote passes with:
[4] +1 (ningjiang, davsclaus, bvahdat, mueller)
[0] -1
I wil
, Hadrian Zbarcea wrote:
The vote passes with:
[10] +1 (joed, bvahdat, joed, cschneider, cmueller, raulk, janstey, dkulp,
ningjiang, hadrian)
[1] +1 - non-binding (ceposta)
[0] -1
I will proceed with publishing the artifacts today and make public
announcement of the release tomorrow, after the mirrors
Willem, if that problem was so important to you to block a release then
it needs to be fixed. Until it's fixed I will -1 a release. It either is
important or it isn't.
Hadrian
On 02/20/2014 12:26 PM, Willem Jiang wrote:
Hi Dan,
Thanks for the inputs.
The annotation is already RetentionPolic
iang
Weibo: 姜宁willem
On February 20, 2014 at 11:03:42 AM, Hadrian Zbarcea (hzbar...@gmail.com) wrote:
While we had enough votes to pass this release I chose not to. I
don't
have cycles to cut another release in the next week week or so.
This
release is also blocking the AMQ release.
stuff with 1.6 if it's that important to
you guys. There are many users who rebuild Camel from sources and what
you are saying is that while we support 1.6, we actually don't.
Cheers,
Hadrian
On 02/19/2014 09:53 PM, Hadrian Zbarcea wrote:
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.12.3, a patch release coming
with about 128 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
Staging repo:
h
Babak, per the ASF policy we can release 2.12.3 even with -1s.
However, I usually shoot for consensus. Here's what I am going to do in
this case, because yours is the only -1 with an overwhelming majority of
+1s. I'll give it another 12 hours and if nothing changes I will close
the vote and rel
thanks to all contributors,
Hadrian
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.11.4, a patch release coming
with about 26 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=1232
Forgot my +1.
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.11.4, a patch release coming
with about 26 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
Staging repo:
h
Babak,
We're past the 72 hours mark and I would like to close this vote with a
consensus is possible. Do you still think we have an issue, or you want
to consider reverting your vote?
Cheers,
Hadrian
On 02/17/2014 05:06 AM, Babak Vahdat wrote:
Hi Willem,
can you please elaborate your expl
This is a vote to release Apache Camel 2.11.4, a patch release coming
with about 26 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
Staging repo:
https://repository.apache.org/content/repositories/orgapachecamel-1003/
T
This is a vote to release Apache Camel 2.12.3, a patch release coming
with about 128 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
Staging repo:
https://repository.apache.org/content/repositories/orgapachecamel-1002
Tarb
Hi,
I am planning on releasing patch versions later in the afternoon today
(it may spill into the weekend). Any objections or other patches you
still need to get in?
Cheers,
Hadrian
Dan,
I assume this is re: CAMEL-5891 [1]. I assigned it to you. Please add
the issue id in the commit comment.
Cheers,
Hadrian
[1] https://issues.apache.org/jira/browse/CAMEL-5891
On 02/07/2014 01:10 PM, dk...@apache.org wrote:
Updated Branches:
refs/heads/master f74e28160 -> 5ecbfe920
I have a few issues assigned to me. Please don't move them, the
camel-kafka component in particular (but not only).
Thanks,
Hadrian
On 02/04/2014 12:33 PM, Christian Müller wrote:
I just upgraded my local workspace to CXF 2.7.9 which I would like to see
in the next Camel versions [1]. The tes
,
Hadrian
On 01/07/2014 10:09 PM, Hadrian Zbarcea wrote:
A bit overdue, this is a vote to release Apache Camel 2.11.3, a patch
release coming with about 116 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325024
Staging
+1
On Tue, Jan 7, 2014 at 7:09 PM, Hadrian Zbarcea wrote:
A bit overdue, this is a vote to release Apache Camel 2.11.3, a patch
release coming with about 116 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325024
Staging
Even better. Thanks,
Hadrian
On 01/12/2014 07:04 PM, Babak Vahdat wrote:
Hi
Actually we've already marked this as deprecated since ages (see the section
"... is *@deprecated*."):
http://camel.465427.n5.nabble.com/CONF-Apache-Camel-gt-Camel-Maven-Plugin-td5715931.html
However as a result of t
This was a discuss thread. Since it wasn't a vote, there was no formal
[result] message. I assume that the reason for the end of discussion is
that nobody had anything to add. The not so lazy consensus was to remove
the camel:dot goal.
The only one who expressed an opinion as to when to remove
A bit overdue, this is a vote to release Apache Camel 2.11.3, a patch
release coming with about 116 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325024
Staging repo:
https://repository.apache.org/content/repositories/orgapachec
There are two outstanding vetoes. Please revert the patch until the
conclusion of this discussion.
Hadrian
On 12/01/2013 03:46 AM, Rob Davies wrote:
dk...@apache.org wrote
Having no way for this PMC to control the display of the Camel route *IS*
a technical justification. If we as a PMC wa
While we discuss, with two vetoes pending, first step is to revert the
patch.
Cheers,
Hadrian
On 11/30/2013 02:35 AM, Robert Davies wrote:
It seems a couple of people are getting a head of themselves.
Firstly, the -1 vote of Dan and Hadrian are invalid without a technical
justification, an
The camel:dot goal provided by the camel-maven-plugin has not been
maintained in 5+ years, produces poor quality output and, most
importantly, doesn't seem to be used. I propose to remove it.
Hadrian
Actually, funny you should ask. The camel:dot goal (DotMojo.java) has
not been maintained for 5+ years, is not used and produces output of
very poor quality.
We agreed to remove the camel console from the camel distro and RedHat
intends, I assume, to promote the hawtio solution. Other parties
My mistake. Sorry and thanks David for reporting so quickly. It's fixed
now, the site should refresh in a couple of hours.
Hadrian
On 11/27/2013 07:43 PM, David Karlsen wrote:
The release page has wrong link (version) into JIRA for the fixed issues
28. nov. 2013 01:03 skrev følgende:
The Ap
Done. Next is camel-2.11.3 this week.
Hadrian
On 11/22/2013 10:44 PM, Hadrian Zbarcea wrote:
The release is done, but for some reason the apache repo doesn't let me
close the staging repo:
The server did not close the staging repository.
Nexus returned an error: ERROR 502: Proxy Error
,
Hadrian
On 11/22/2013 10:52 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.12.2, a patch release coming
with about 143 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325018
Staging repo:
h
+1
Hadrian
On 11/22/2013 10:52 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.12.2, a patch release coming
with about 143 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325018
Staging repo:
h
the binary as Apache Camel 2.12.2
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Thanks,
Hadrian
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
The release is done, but for some reason the apache repo doesn't let me
close the staging repo:
The server did not close the staging repository.
Nexus returned an error: ERROR 502: Proxy Error
I'll try again in the morning and take it with infra if necessary. I
will start the vote as soon as t
For some reason, the context for me is localhost/camel-1.
I fixed the test, but I am curious how this works for others now.
This is I think/hope the last failing test and now I can cut the release.
Hadrian
On 11/20/2013 10:42 AM, davscl...@apache.org wrote:
Updated Branches:
refs/heads/mas
Longer day than I hoped. I think a new bug was introduced this week.
Other than that I looks like we're ready for the release. I am planning
on building it tomorrow.
Claus any luck with CAMEL-6988? Please advice if it could get in this
release or not.
Hadrian
On 11/20/2013 02:23 PM, 7erry
17/2013 07:54 PM, Hadrian Zbarcea wrote:
There are test failure(s) I need to look at:
Are there any other issues you absolutely need in 2.12.2?
Hadrian
On 11/12/2013 08:11 PM, Willem jiang wrote:
+1,
BTW, it looks Camel 2.12.x is catch up the release cycle of Camel 2.11.x.
--
Willem Jian
On Wednesday, November 13, 2013 at 5:13 AM, Christian Müller wrote:
+1
Best,
Christian
On Tue, Nov 12, 2013 at 5:24 PM, Claus Ibsen
wrote:
On Mon, Nov 11, 2013 at 7:52 PM, Hadrian Zbarcea
hzbar...@gmail.com)>
wrote:
I wanted to say the same thing. Maybe even sooner in the month.
For what is worth, the test was failing with all JDKs not just OpenJDK.
Not sure if hardcoding the cipher suite is the best fix in the long run,
but it does work.
Hadrian
On 11/18/2013 09:56 PM, Willem jiang wrote:
Hi Babak,
Thanks for the review, I just updated the code with some suggestio
Good catch Babak. Thanks,
Hadrian
On 11/18/2013 02:59 PM, Babak Vahdat wrote:
Hi
Just spotted couple of things on the commit mailing list of today:
http://git-wip-us.apache.org/repos/asf/camel/diff/000581e6
This commit now makes the following asserts passing:
assertStartsWith((String[]) n
I could
do this next week or so (comming back to a "normal" work load in my day
job...).
Best,
Christian
On Mon, Nov 18, 2013 at 1:54 AM, Hadrian Zbarcea wrote:
There are test failure(s) I need to look at:
Are there any other issues you absolutely need in 2.12.2?
Hadrian
On
, Nov 12, 2013 at 5:24 PM, Claus Ibsen mailto:claus.ib...@gmail.com)> wrote:
On Mon, Nov 11, 2013 at 7:52 PM, Hadrian Zbarcea mailto:hzbar...@gmail.com)>
wrote:
I wanted to say the same thing. Maybe even sooner in the month. How about
shooting to build the release end of this week. I can take c
Will do. The default is 'Major' so pretty much all issues are like that.
Few are changed to a different level (usually to draw attention to
something that has a more serious impact). It's hard to be pedantic with
the issue severities, because, we are a self managed community (like all
others at
I wanted to say the same thing. Maybe even sooner in the month. How
about shooting to build the release end of this week. I can take care of
this release.
Hadrian
On 11/11/2013 01:33 PM, Claus Ibsen wrote:
Hi
I think we should cut a new 2.12.2 release later this month. We have
so far 115 ji
Jan,
Personally I don't think there is a need for one in camel core. As a
framework, camel should stay very simple and provide solutions/helpers
for the common use cases. Such a dsl, while useful in your context adds
unnecessary (imho) complexity for camel. That's the beauty of camel, it
is p
Sounds great!
Hadrian
On 09/26/2013 04:29 PM, Henryk Konsek wrote:
Hi,
People associated with Camel Extra might be interested in this [1] forum thread.
Thanks & laters.
[1]
http://camel-extra.1091541.n5.nabble.com/Camel-Extra-CI-server-at-Cloudbees-td50.html
+1
Hadrian
On 09/19/2013 01:25 AM, Christian Müller wrote:
After 9 days of development, we have a new bug fix release candidate
apache-camel-2.12.1 ready.
It comes with 47 issues resolved: new features, improvements and bug fixes
[1]. You can find the release notes here [2].
We release this ver
+1 (not sure why the reply-to private@)
Hadrian
On 09/15/2013 05:25 PM, Christian Müller wrote:
After 2 month of development, we have a new bug fix release candidate
apache-camel-2.10.7 ready.
It comes with 63 issues resolved: new features, improvements and bug fixes
[1].
You can find the releas
Agree, I'll take care of it this week.
Hadrian
On 09/10/2013 06:00 AM, Claus Ibsen wrote:
Hi
I think its time we cut a new patch release of 2.11 branch. We have
100+ resolved tickets since last release.
And 2.11.1 was released about 2 months ago
http://camel.apache.org/2013/07/17/apache-camel-
What about considering developing in progress work on a branch and only
merge it to a stable branch (master or maintenance) when ready? Using
branches is much easier with git and was one of the reasons to migrate
to git.
My $0.02,
Hadrian
On 08/29/2013 10:21 AM, Claus Ibsen wrote:
Hi Willem
Willem, I believe the new version on the trunk should be 2.13-SNAPSHOT
and the 2.12.1 branch created off of the tag.
Hadrian
On 08/23/2013 05:41 AM, Willem jiang wrote:
I will take care of the OSGi bundle upgrading work.
BTW, I'm planing to use JDK 1.7 to build the release and I will run some
I would strongly suggest building the release with 1.6. I had problems
in the past releasing with a JDK release newer than the oldest supported
one.
I am mostly off the grid until the end of next week (most likely) and I
won't be able to help with a release until then.
My $0.02,
Hadrian
O
The vote passes with:
[8] +1 (ningjiang, davsclaus, hadrian, dkulp, janstey, cschneider,
cmueller, raulk)
[0] -1
I will proceed with publishing the artifacts and the public announcement
of the release.
Many thanks to all contributors,
Hadrian
On 07/09/2013 11:34 PM, Hadrian Zbarcea wrote
+1
Hadrian
On 07/09/2013 11:34 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.11.1, a patch release coming
with about 110 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323967
Staging repo:
h
the binary as Apache Camel 2.11.1
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Thanks,
Hadrian
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Mon, Jul 8, 2013 at 5:24 PM, Hadrian Zbarcea wrote:
I could do it too, got back from vacation.
One of the issues is yours Christian, I will look into it after finishing
this build. The
with less effort than me...
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/chr
n Mon, Jul 8, 2013 at 5:24 PM, Hadrian Zbarcea wrote:
I could do it too, got back from vacation.
One of the issues is yours Christian, I will look into it after finishing
this build. The other one is just doc, I think.
Running a full test now, all good so far (almost forgot how long it
er: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Jun 28, 2013 at 12:06 AM, Hadrian Zbarcea
Hi Christian,
Next week I'll be
Hi Christian,
Next week I'll be in vacation, but I can do the 2.11.1 after I come
back. It should be ok, I assume the 22 issues will not be all resolved
next week.
Cheers,
Hadrian
On 06/27/2013 05:02 PM, Christian Müller wrote:
We agreed to not build the PDF manual starting with Camel 2.12
Give the fact that it uses precious compile time, I would drop the html
manual too. It's not as well formated as the PDF one and equally useless.
Just my $0.02,
Hadrian
On 06/27/2013 12:30 PM, Christian Müller wrote:
+1 for #5 but would like to keep html manual.
Best,
Christian
Sent from a m
#5 +1 agree
Hadrian
On 06/27/2013 10:07 AM, Claus Ibsen wrote:
I vote for #5
It will just keep haunting us in the future. With new problems etc.
Its 2013 and people read online docs / google / stackoverflow / watch
videos / etc.
The camel pdf manual is not a good manual but just a big dump of
/www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Tue, Jun 25, 2013 at 3:37 AM, Hadrian Zbarcea wrote:
-1 (reluctantly)
* Checking out the tag I see that all poms use 2.10.5-SNAPSHOT. Not good
for a release.
* Building from the tag went fine (didn&
-1 (reluctantly)
* Checking out the tag I see that all poms use 2.10.5-SNAPSHOT. Not good
for a release.
* Building from the tag went fine (didn't run all tests yet, but I plan
to tomorrow). However, in ./tests, both camel-itest-osgi and
camel-itest-karaf are excluded from the build, and what'
edin.com/pub/christian-mueller/11/551/642
On Sun, May 26, 2013 at 7:10 PM, Hadrian Zbarcea
wrote:
We have some time, as I am still waiting for infra to resolve the
git
mirror issue and I need to switch the release builds to use git tags
instead of svn.
Cheers,
Hadrian
On 05/25/2013
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
try...
Christian
Sent from a mobile device
Am 24.05.2013 13:52 schrieb "Claus Ibsen" :
Hi
Any news on the possibility of a 2.10.5 release.
The next release will actually be out 50th release. So that is a good
milestone to reach :)
On Wed, May 15, 2013 at 2:32 PM, Hadrian Zbarcea
wr
Yep, it's about time. I will take care of the necessary changes to be
build system and get ready for the release. What are the issues that
still need to be finished for 2.10.5? Let's start closing down.
Hadrian
On 05/15/2013 03:10 AM, Claus Ibsen wrote:
Hi
Its been 2.5 months ago we releas
The notifications still go to commits@, but the subject is "git commit:
[comment]". Just if anybody wonders.
Cheers,
Hadrian
On 05/06/2013 03:46 PM, Christian Müller wrote:
Done.
My first commit into our brand new Git repo was a revert... :-(
Best,
Christian
On Thu, May 2, 2013 at 10:36 P
33 AM, Hadrian Zbarcea wrote:
I added a comment to the INFRA jira, we should be back in business
shortly. Thanks for everybody's patience.
Hadrian
On 05/06/2013 09:47 AM, Johan Edstrom wrote:
Cloned nicely. (And danged fast).
On May 6, 2013, at 7:45 AM, Christian Müller
wrote:
The Git
e too (master, branches, tags).
I tried to update our CI builds to use our new Git repository, but I got an
exception. There is also no explanation at https://git-wip-us.apache.org.
Could someone try whether he has more luck than me...
Best,
Christian
On Mon, May 6, 2013 at 3:43 PM, Hadrian Zb
Thanks Jon. Could we please get another nod?
Hadrian
On 05/06/2013 07:24 AM, Jon Anstey wrote:
Git repo at https://git-wip-us.apache.org/repos/asf/camel.git looks good to
me.
On Sun, May 5, 2013 at 10:41 PM, Hadrian Zbarcea wrote:
The migration is done. It looks ok to me and I would
release and I can take care of that.
Do we need to give more time for testing the repo, or we have enough
committers comfortable with the change?
Hadrian
[1] https://issues.apache.org/jira/browse/INFRA-6197
On 04/24/2013 04:36 PM, Hadrian Zbarcea wrote:
Actually, we may save some time and skip a
Hi,
You can of course implement a processor (or an endpoint) that
encapsulates an execution engine powered by scxml (or bpel, or other
language for that matter).
That discussion however took place in a different context, externalizing
the dsl. But you are correct, we could implement support
Lukasz,
It looks good, it's not that big actually. Could you please create a JIRA?
Did you use it with camel-mail to send invites? Do you have some more
complex example as well?
Cheers,
Hadrian
On 04/25/2013 11:39 AM, Hadrian Zbarcea wrote:
Interesting contribution. I will take a
Interesting contribution. I will take a look later today. I did some
work with ics data in the past.
Cheers,
Hadrian
On 04/24/2013 04:39 PM, Łukasz Dywicki wrote:
Hey all,
I would like to ask if camel project is interested in picking up another
component to source repository. The component I
+1
Hadrian
On 04/24/2013 05:32 PM, Christian Müller wrote:
After 6 weeks of development, we have a new patch release candidate
apache-camel-2.9.7 ready. It comes with 14 issues resolved [1].
This will be the last planned Camel 2.9.x release. We will discontinue the
support for the camel-2.9.x br
Actually, we may save some time and skip a vote, let's see if infra asks
for one. I created an issue for infra as a first step [1].
Cheers,
Hadrian
[1] https://issues.apache.org/jira/browse/INFRA-6197
On 04/24/2013 03:57 PM, Hadrian Zbarcea wrote:
Will do. Let's start with a f
Will do. Let's start with a formal vote.
Hadrian
On 04/24/2013 03:51 PM, Christian Müller wrote:
Hi Hadrian!
Do you consider to drive this topic after you collect many +1? ;-)
Best,
Christian
On Wed, Mar 27, 2013 at 9:01 PM, Hadrian Zbarcea wrote:
Would that something that s
Agree. Let's shoot for next week, end of this month.
Hadrian
On 04/22/2013 07:03 AM, Christian Müller wrote:
+1 for releasing it shortly.
Sent from a mobile device
Am 22.04.2013 09:36 schrieb "Claus Ibsen" :
Hi
When 2.11.0 is GA, we should IMHO do a last 2.9.x release, and then
retire that b
I would move to git first. Branching is also easier, imho.
$0.02,
Hadrian
On 04/22/2013 03:30 AM, Claus Ibsen wrote:
Hi
We should setup a branch for 2.11
https://svn.apache.org/repos/asf/camel/branches/
And I think in the process there is something to setup for svnmerge to
have that working a
this
release now...
Best,
Christian
On Mon, Apr 8, 2013 at 4:11 PM, Hadrian Zbarcea wrote:
- No idea how/why Maven generated this folder:
https://svn.apache.org/repos/**asf/camel/tags/camel-2.11.0/**trunk/<https://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/trunk/>
My guess wo
- No idea how/why Maven generated this folder:
https://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/trunk/
My guess would be that Christian had some trouble with release:prepare
and redid it without removing the tag. Happened to me before and I had
to redo the release.
Hadrian
This has been mentioned a few times, but no agreement was reached.
Actually we should drop the whole MEP as it makes little to no sense. It
could be a hint at best. For me the rationale has little to do with JBI.
The MEP only makes sense for an Endpoint (i.e. Producer or Consumer) but
not for t
I think there is a problem with camel-bindy as well. I am looking into
it today.
Hadrian
On 04/02/2013 12:37 PM, Christian Müller wrote:
I think it would be good if we could include CAMEL-6218 into Camel 2.11.0.
May an ActiveMQ expert could have a look into it?
Best,
Christian
On Tue, Apr
public on Mon, so I could build 2.11.0 on Tue.
Cheers,
Hadrian
On 03/28/2013 08:18 AM, Hadrian Zbarcea wrote:
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
arded. Has been touched in 5 years.
True.
All of this remains in SVN's history forever so not a big deal. If we ever
need any of it back, it will always be there.
Dan
Best,
Christian
On Wed, Mar 27, 2013 at 9:01 PM, Hadrian Zbarcea wrote:
Would that something that sounds appealing
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 wrote:
Christian, do you want to build this release or you want me to do it?
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
forum.
[1]
http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=38
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
www.redhat.com
Blog: http://willemjiang.blogspot.com (
http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, March 27, 2013 at 9:26 AM, Hadrian Zbarcea wrote:
I've been asked today by a
om (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, March 27, 2013 at 9:26 AM, Hadrian Zbarcea wrote:
I've been asked today by a fellow ASFer if it's ok for us to dist
ll have to pull the camel-spring-neo4j
component out and host it maybe at camel-extra, but we'll see in the
coming days.
Cheers,
Hadrian
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
amqp is failing for me. Will look into it this afternoon.
Hadrian
On 03/15/2013 02:48 AM, Claus Ibsen wrote:
On Thu, Mar 14, 2013 at 3:29 PM, Claus Ibsen wrote:
Hi
Okay I fixed a few issues with the Karaf features so they all now work
and the camel-itest-karaf all passes on linux and windows
to test and vote.
Hadrian
On 03/04/2013 11:51 PM, Hadrian Zbarcea wrote:
We have a new patch release candidate apache-camel-2.9.6 ready. It comes
with approximately 63 issues resolved: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content
Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Here's my +1.
Hadrian
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323592
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.
It won't propagate to the mirrors until tomorrow though.
Hadrian
On 03/04/2013 09:21 PM, Christian Müller wrote:
Great thanks!
Best,
Christian
On Tue, Mar 5, 2013 at 3:15 AM, Hadrian Zbarcea wrote:
Yes, that's what I was doing now. I am also releasing 2.9.6 this evening.
Cheer
ise I can volunteer here...
Best,
Christian
On Tue, Feb 26, 2013 at 7:08 AM, Hadrian Zbarcea wrote:
Result passes with:
[4] +1 (cschneider, dkulp, cibsen, hadrian)
[0] -1
[1] +0 (bvahdat)
The artifacts will be released to the public maven repo immediately,
followed by the ASF site and mirro
/22/2013 09:16 AM, Hadrian Zbarcea wrote:
We have a new patch release candidate apache-camel-2.10.4 ready. It
comes with approximately 105 issues resolved: improvements and bug fixes
[1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-294/
The
1 - 100 of 1517 matches
Mail list logo
