> On Mar 25, 2016, at 10:42 PM, Claus Ibsen wrote:
>
> Hi Antoine
>
> Yay sounds good. What do you fancy working with?
>
> We got stuff around OSGi such as
>
> - upgrading the tests to be karaf 4.x based
> - drop karaf 2.x
> - upgrade to OSGi 5.0
Looks like Raul is on top of it. I have some O
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/920
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
+1 (binding).
Tested on some of my personal projects.
Thanks Gregor :-)
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Monday, March 28, 2016 12
On Tue, Mar 29, 2016 at 1:04 AM, Raul Kripalani wrote:
> Thanks a lot Claus!
>
> Given that we now make no distinction between bundles and standard JARs
> through the packaging type, I was having the OSGi MANIFEST generation
> triggered for bundles where its irrelevant, e.g. camel-grape,
> camel-s
What do you think of this approach?
MulticastProcessor should pass in it’s own AsyncCallback (or attach a
Synchronization if you perfer) where on done() we submit the Exchange to be
aggregated. That way if the route is async no threads are blocked waiting for a
response, essentially it would be
What do you think of this approach?
MulticastProcessor should pass in it’s own AsyncCallback (or attach a
Synchronization if you perfer) where on done() we submit the Exchange to be
aggregated. That way if the route is async no threads are blocked waiting for a
response, essentially it would be
The Apache Jenkins build system has built Camel.trunk.notest (build #2704)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2704/
to view the results.
Camel riders,
I'm seeing an issue caused by the MulticastProcessor not handling async
routing end-to-end. It does use its own threadpool to process its routing
tasks, as well as to perform the aggregation (on-the-fly).
However, during all that time, the calling thread is blocked waiting for
the m
Thanks a lot Claus!
Given that we now make no distinction between bundles and standard JARs
through the packaging type, I was having the OSGi MANIFEST generation
triggered for bundles where its irrelevant, e.g. camel-grape,
camel-spring-boot, many examples, etc. So I added a profile which is
activ
Hello Seth,
please have a look at this page:
http://camel.apache.org/how-do-i-edit-the-website.html
I also went through this process recently, it's quite fast.
Bye
Wolfram
On Mon, Mar 28, 2016, at 05:06 PM, seth sorensen wrote:
> Hello,
> I would like to be given permission to edit the wiki. I
Hello,
I would like to be given permission to edit the wiki. I have found an error
with the documentation, and would like to correct it.
Thanks,snesneros
I’d like to try the bnd-maven-plugin, but I can’t get the build to work on the
branch.
When I run
mvn -DskipTests clean install
I get
[ERROR] Failed to execute goal
org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default)
on project maven-plugins: Artifact does not conta
Hi Everyone:
This is a vote to release Apache Camel 2.15.6, a new patch release
that includes ~37 fixes and improvements. This will be the last
official patch release for the 2.15.x branch.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334208&styleName=&project
Hi Claus,
Yes, the checkstyle profile is activated by default when we make a
release, see https://github.com/apache/camel/blob/master/pom.xml#L293:
[...]
-Prelease,enable-schemagen,apt,sourcecheck,hibernate
[...]
It's usually just a few minor fixes, and I mostly try to start fixing
these issues
GitHub user oalles opened a pull request:
https://github.com/apache/camel/pull/920
CMComponent must not rely on dependency injection
CMComponent must not rely on dependency injection as it should work out of
the box.
README.md is updated in order to reflect new component na
15 matches
Mail list logo