+1
Best,
Christian
Am 03.04.2016 21:28 schrieb "Gregor Zurowski" :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.16.3, a new patch release
> that includes 75+ fixes and improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334721&project
Tested out installing various camel components into Karaf 3.x, appears to
work fine.
+1 (non-binding)
On 6 April 2016 at 12:46, Jon Anstey wrote:
> +1
>
> On Sun, Apr 3, 2016 at 4:57 PM, Gregor Zurowski
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 2.16.3, a new pa
+1
On Sun, Apr 3, 2016 at 4:57 PM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.16.3, a new patch release
> that includes 75+ fixes and improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334721&projectId=12311
Thanks Raul -
I didn’t realize the SNAPSHOTs were always deployed. I tried using the
SNAPSHOT repository quite a while ago, and it didn’t ever seem to be very
current.
Regardless, given the way we generate our Import-Package header today (we don’t
use SNAPSHOT there), the versions will resolv
On Wed, Apr 6, 2016 at 4:35 PM, Quinn Stevenson wrote:
> Also, since Camel doesn’t really “release” any SNAPSHOT builds, this is a
> decision that only effects the development community IMO. People
> building/using SNAPSHOT versions must understand what’s going on anyway -
> either way will work
During a discussion in the Camel dev@ list about possibly adopting the
bnd-maven-plugin, a contributor noticed differences in the way that package
export versions are computed between Felix' maven-bundle-plugin and the
former.
http://camel.465427.n5.nabble.com/DISCUSS-Moving-from-maven-bundle-plug
I’d like to mention one area where the default behavior of the bnd-maven-plugin
with SNAPSHOTs is very useful/helpful.
As stated before, the bnd-maven-plugin sets the Bundle-Version header to
X.X.X. by default. When you’re installing/updating bundles in
Karaf, this makes it easy to determine i
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/933
CAMEL-9587 - camel-restlet - Make it easy to turn on gson or jackson
With this PR one can explicit set the converters to use with:
```
from("restlet:?enabledConverters=JacksonCon
In my opinion, the benefits of the bnd-maven-plugin vs the maven-bundle-plugin
are:
- Easier configuration
You configure the bnd-maven-plugin just like you configure BND - there isn’t
any strange XML mapping to BND configuration. Also, it keeps the OSGi
configuration separate from the build c
On Wed, Apr 6, 2016 at 12:29 AM, David Jencks <
david_jen...@yahoo.com.invalid> wrote:
> I don’t know how camel is doing release versions after a period of
> development, but recall that osgi version 1.2.3.SNAPSHOT is after 1.2.3, so
> if you use normal maven release practices and version the expo
+1
Dan
> On Apr 3, 2016, at 3:27 PM, Gregor Zurowski wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.16.3, a new patch release
> that includes 75+ fixes and improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334721&proje
On 4/6/16 1:53 AM, Claus Ibsen wrote:
Yeah all the sister Apache projects like Karaf / ServiceMix / CXF /
ActiveMQ etc are also using it. Though it begs the question - why 2
plugins? Why cant they work together and make 1 good plugin. There
adoption of OSGi do not need more confusion and projec
On 4/5/16 6:29 PM, David Jencks wrote:
I don’t know how camel is doing release versions after a period of development,
but recall that osgi version 1.2.3.SNAPSHOT is after 1.2.3, so if you use
normal maven release practices and version the exported packages the same as
the bundle version (a te
GitHub user erwelch opened a pull request:
https://github.com/apache/camel/pull/932
CAMEL-9768 HTTP[4] component disableStreamCache issue
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/erwelch/camel CAMEL-9768
Alternatively you
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/931
[CAMEL-9825] Exclude CDI generated proxies from context tracker
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-9825
Alter
I will take care of this.
I think this feature is very important :-)
Thank you for your time! :-)
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On
Ah sorry there was a bug in the maven tooling.
It should use == and not != in a check
I will fix it later as I am in the middle of something. You can also
fix it if you got the time
It should be
if (before == after) {
missingAdocFiles.add(dir);
}
Instead of
if (before != after) {
miss
I've executed an mvn clean install of all Camel and then run mvn clean install
on catalog.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesd
On Wed, Apr 6, 2016 at 10:01 AM, Andrea Cosentino
wrote:
> Hi Claus,
>
> It's a bit weird.
>
> I run mvn clean install and from the list it seems we don't have docs, but
> for example on
>
> https://github.com/apache/camel/tree/master/components/camel-ahc/src/main/docs
>
> We have already an .ado
Hi Claus,
It's a bit weird.
I run mvn clean install and from the list it seems we don't have docs, but for
example on
https://github.com/apache/camel/tree/master/components/camel-ahc/src/main/docs
We have already an .adoc file.
Actually I've arrived at camel-hdfs.
--
Andrea Cosentino
--
On Wed, Apr 6, 2016 at 9:38 AM, Claus Ibsen wrote:
> And btw we should consider a structure naming for the src/main/docs
> folder so we can differentiate what the docs are for as a Maven module
> may include both components / data formats / languages etc.
>
> So I would consider doing something li
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/929
---
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
I agree with you guys. I have doubts whether going the bnd-maven-plugin
brings in any actual benefits vs our current setup.
Now that we use the "lightweight" process anyway (no 'bundle' extensions,
just generating the manifest), both approaches got to be functionally
equivalent, aside from minor d
And btw we should consider a structure naming for the src/main/docs
folder so we can differentiate what the docs are for as a Maven module
may include both components / data formats / languages etc.
So I would consider doing something like
src/main/docs
- readme.md - a summary of what this mav
Hi
I added a report output when building camel-catalog, that prints which
camel component modules that do not have any src/main/docs files.
This can help us keep an eye on how many we have yet to do.
Mind it only reports on directory level. So if a module has such as 3
components then it will re
On Wed, Apr 6, 2016 at 9:06 AM, Achim Nierbeck wrote:
> It's something I don't get either, why they didn't work on the
> maven-bundle-plugin, but that's something you need to ask the bnd folks.
> blueprint isn't dead btw. just the website really really sucks :D
>
Yeah we know the feeling with a p
It's something I don't get either, why they didn't work on the
maven-bundle-plugin, but that's something you need to ask the bnd folks.
blueprint isn't dead btw. just the website really really sucks :D
regards, Achim
2016-04-06 8:53 GMT+02:00 Claus Ibsen :
> On Wed, Apr 6, 2016 at 8:49 AM, Achim
27 matches
Mail list logo
