R: camel git commit: Fix build after solr/lucene upgrade

Sorry Claus. My mistake Inviato da Yahoo Mail su Android Il ven, 1 apr, 2016 alle 7:09, davscl...@apache.org ha scritto: Repository: camel Updated Branches:   refs/heads/master 7a1abb386 -> afd200a59 Fix build after solr/lucene upgrade Project: http://git-wip-us.apache.org/repos/asf/ca

Camel.2.17.x.notest - Build # 11 - Failure

The Apache Jenkins build system has built Camel.2.17.x.notest (build #11) Status: Failure Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/11/ to view the results.

Camel.2.16.x.notest - Build # 293 - Still Failing

The Apache Jenkins build system has built Camel.2.16.x.notest (build #293) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.2.16.x.notest/293/ to view the results.

Camel.trunk.notest - Build # 2707 - Still Failing

The Apache Jenkins build system has built Camel.trunk.notest (build #2707) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/2707/ to view the results.

Re: Where is the camel.osgi.version.clean property defined in the build?

It's defined by the clean goal of the bundle plugin. Check out the definition in the parent pom. Raúl.

Where is the camel.osgi.version.clean property defined in the build?

I’m working on https://issues.apache.org/jira/browse/CAMEL-9754 and I’m in the process of converting the bundle manifest configuration, but I can’t seem to figure out where the camel.osgi.version.clean property is defined during the build process. Can someone help me out?

[ANNOUNCEMENT] Apache Camel 2.15.6 Released

The Camel community announces the immediate availability of the new patch release Camel 2.15.6, the last planned release for the 2.15.x branch. This release contains a total of 37 bug fixes and improvements applied in the past months by the community on the Camel 2.15.x branch. The artifacts are p

[RESULT] [VOTE] Release Apache Camel 2.15.6

This vote passes with the following results: +1 binding: 5 (Andrea Cosentino, Christian Müller, Claus Ibsen, Daniel Kulp, Gregor Zurowski) I will publish the artifacts for Camel 2.15.6 shortly. Due to the fact that this release is EOL now, should I still update the download pages, or should I ra

Re: [VOTE] Release Apache Camel 2.15.6

+1 (binding) Gregor On Mon, Mar 28, 2016 at 12:29 PM, Gregor Zurowski wrote: > 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:

Re: [DISCUSS] - Thoughts on Apache Camel 2.18 and towards 3.0

I recently worked on some projects that also need OSGi settings and found an interesting thing. It seems the easiest way to get the exports, imports and other OSGi settings right is not to use central defaults and instead do all settings per project while relying on defaults as much as possible.

[GitHub] camel pull request: Fix camel core test on windows

Github user PascalSchumacher closed the pull request at: https://github.com/apache/camel/pull/924 --- 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 featur

Re: Usage of Lambdas in our Maven build (jdk8-lambdas branch)

Hi Okay I fixed some missing files in camel-core that somehow the old way included. Some of those missing files causes unit tests to fail in spring, that test loading some model metadata from camel-core JAR. That all now works. So we are left with 3 components not working in OSGi due some doubl

[GitHub] camel pull request: Fix camel core test on windows

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/camel/pull/924 Fix camel core test on windows You can merge this pull request into a Git repository by running: $ git pull https://github.com/PascalSchumacher/camel fix_camel_core_test_on_windows A

Cleanup remote branches

We got a bunch of remote branches that has been merged to master, or is no longer in use. I propose to remove all branches that are not camel release branches or master itself. And the old trunk branch (should it be kept?) These are the ones: origin/CAMEL-4232 origin/CAMEL-6555 origin/camel-

[GitHub] camel pull request: CAMEL-9776 : camel-braintree: add uri param to...

Github user lburgazzoli closed the pull request at: https://github.com/apache/camel/pull/922 --- 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

Re: Usage of Lambdas in our Maven build (jdk8-lambdas branch)

Hi I see this little WARN when its building camel-parent [INFO] --- maven-bundle-plugin:3.0.1:manifest (bundle-manifest) @ camel-parent --- [WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle] We should filter out packaging=pom if possible so the bundle plugin do not run o