The Apache Jenkins build system has built Camel.2.14.x.notest (build #181)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/181/
to view the results.
There has been some discussion about camel-extras license policy on IRC
and in CAMEX-69[1]
Summarizing it, there are three policies that are relevant, two are
documented, one is more ambiguous:
- Google Code allows projects to have any OSI approved license[2],
anything without such a license is
I am wondering if there is a way to avoid this awkward situation.
When you install camel-cxf 2.15.2 feature on a freshly setup karaf
3.0.3, it will end up with two versions of ServiceMix Stax API
bundles.
karaf@root()> feature:repo-add camel 2.15.2
Adding feature url mvn:org.apache.camel.karaf/ap
We have links to 3rd party .. whatever related to Camel at the user stories page
http://camel.apache.org/user-stories.html
The external component list is fine to add 3rd part, but we have to
make sure the license is correct, and that those projects are of more
common interest and that they are act
What is the policy about adding third-party components to the wiki?
Is it only for components in the main Camel repository?
Are things that belong in Camel-extra welcome in the wiki?
What about components that are not part of either repository, e.g.
because of dependencies or just because the
