Would this have gone in had it been a regular git hub project?
That's really the only question you need to ask yourself, right?
Sent from my pressure cooker.
On Oct 18, 2013, at 18:25, Christian Müller wrote:
> I'm sure you know the project much better than me, but if you have a look
> at the d
Christian,
I commited fix for this both on the master as well as the 2.12.x branch.
Would you please give it another try to see if you can still reproduce the
test failures you mentioned by your previous posts?
Babak
Christian Mueller wrote
> Really good catch!
>
> Best,
>
> Christian
> -
I'm sure you know the project much better than me, but if you have a look
at the dependency tree for camel-leveldb 2.12.1:
[INFO] org.apache.camel:camel-leveldb:bundle:2.12.1
...
[INFO] +- org.fusesource.leveldbjni:leveldbjni-all:jar:1.7:compile
[INFO] | +- org.fusesource.leveldbjni:leveldbjni-os
Really good catch!
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Oct 18, 2013 at 11:47 PM, Baba
Is there an option in apache camel to derive the userid, if the route is
started manually via Jconsole?
Basically, I have defined an retry route for exceptions that has to be
manually triggered. I would like to capture the user detail for audit
purposes.
Thanks
--
View this message in conte
The root cause of the problem for the failing JPA test is CAMEL-5932 through
which we started sharing the *same* EntityManager object across JpaEndpoint,
all it's created producers and consumers which is wrong! JPA 2.0 Spec,
section 7.2:
An entity manager must not be shared among multiple concurre
Hi,
I'm currently working on a Camel CDI project using CXF/ActiveMQ endpoint
but when CXF endpoint creates the CamelExchange and Camel creates the
UnitOfWork, I get a NPE
https://gist.github.com/7044362
https://gist.github.com/7044297
I suspect that for a reason that I don't know the Exchange is
Hi
Yeah Karaf is a bit more tricky, as just because the feature file
validates succesful, and the features can be installed one by one in
Karaf, does not mean that they actually work.
We do have a bunch of integration tests in camel-itest-osgi but not
for every components.
So in this case camel-
Not every project has 3 digits for their versions. Some have only 2.
And these projects may do bug fix releases where upgrading is safe/compatible.
So when a 2 digit project does a release, then it can be a bug fix
release like leveldb 1.7 to 1.8 is.
For example you can try
http://vdiff.notsoclev
Is this minor dependency upgrade in a Camel micro release also because of
an issue with Leveldb in Camel 2.12.1? Do we have an issue for this?
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apa
Hi All,
i have created one sample web service and deployed in servicemix 4.5.2. i am
able to get the url and client java using getting response:
i am creating another project to consume the webservice but i am getting
error. Source and error is attached.
-
ISimpleWebs
David,
please use the user forum for this kind of questions as we describe at [1].
Can you please also subscribe to the mailing list as we describe here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the
Thanks Claus, I wasn't aware of this issue. May I overlooked the JIRA?
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller
Tracy this is a really nice tool, thanks for creating this.
I added a link to it to our release notes so people is able to use
this tool as its much more useful as you can pick 2 versions for
compare.
Then they can pick their old version and the new version to see the diff.
On Sun, Sep 15, 201
It is good to avoid minor dependency updates in Camel micro releases,
and this should be kept as true as possible especially with main
dependencies,
but with the big fauna of dependencies of the project it is best to have
flexibility over this rule to avoid paralysis :-)
A better commit message ho
15 matches
Mail list logo