On Wed, Apr 6, 2016 at 8:49 AM, Achim Nierbeck wrote:
> Hi,
>
> just wanted to give my 2 cents here.
> I'm watching the bnd-maven-plugin for a while now, from my perspective it's
> not quite there yet, that's why I would stick with the maven-bundle-plugin
> for a while.
>
Yeah all the sister Apac
Hi,
just wanted to give my 2 cents here.
I'm watching the bnd-maven-plugin for a while now, from my perspective it's
not quite there yet, that's why I would stick with the maven-bundle-plugin
for a while.
regards, Achim
2016-04-06 7:46 GMT+02:00 Claus Ibsen :
> Hi
>
> It all sound promising. B
Any further votes for this release?
Thanks,
Gregor
On Sun, Apr 3, 2016 at 9: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
There is some pros with being an endpoint configuration only, as it
can make it easy for tooling and some developers to use it (when they
are used to configure uris, and just use from -> to -> to etc). I
guess the bit unusual part is that you refer to endpoint by id's which
is not so commonly in us
On Mon, Apr 4, 2016 at 6:22 PM, Raul Kripalani wrote:
> That was my exact same thought when I took a stab at the camel-hystrix
> component myself:
> https://github.com/apache/camel/commits/feature/camel-hystrix.
>
> For me, Hystrix is not an endpoint but a mechanism to deal with failure, no
> matt
Thanks Claus to point this out, on it!
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
> On Apr 6, 2016, at 12:58 PM, Claus Ibsen wrote:
>
> -1
>
> There is already an exchangePattern option from the DefaultEndpoint.
>
> Can you not use that, instead of inve
Hi
It all sound promising. But there is plenty of changes already for
2.18 in the build system. We should IMHO keep this version as-is to
avoid too many changes. Building OSGi bundles is really complex for a
project the size as Apache Camel. We need to get what we have now out
to the community.
C
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/928
---
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
There is already an exchangePattern option from the DefaultEndpoint.
Can you not use that, instead of inventing a new duplicate option?
On Wed, Apr 6, 2016 at 4:35 AM, wrote:
> Repository: camel
> Updated Branches:
> refs/heads/master 0437f7db6 -> 92becd2a9
>
>
> [CAMEL-9821]add mep uri
I have a need to listen to the FTP server. Whenever there is a file in FTP
location I need to get callback. How can I implement it with Camel FTP.
I have many FTP servers to subscribe and listen to the new files. When there
are new files I need to ftp them to local folders.
--
View this message
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 terrible idea, but IIUC what you are doing)
I did manage to get the bnd-maven-plugin to generate the Export-Package header
as it is today - with “.SNAPSHOT” on the version - but I had to add a
packageinfo file to every exported package (as described by the snippet posted
below) - they had the same content, but I had to put them there. Th
On Tue, Apr 5, 2016 at 11:00 PM, Matt Pavlovich wrote:
> I was ruminating about this as well-- I agree its not exact; however, is
> there any real impact? The bundle version is indicated by the SNAPSHOT.
> How would the package export having the .SNAPSHOT qualifier (which would
> not impact any
I was ruminating about this as well-- I agree its not exact; however, is
there any real impact? The bundle version is indicated by the
SNAPSHOT. How would the package export having the .SNAPSHOT qualifier
(which would not impact any wiring) have any undesirable impact?
On 4/5/16 4:48 PM, Rau
I quoted the wrong part of your email, but the point still stands.
With regards to the package exports, we do need to preserve the indication
that the module is a snapshot. Otherwise the resulting export is
indistinguishable from the final version IMHO.
Cheers,
*Raúl Kripalani*
PMC & Committer @
On Tue, Apr 5, 2016 at 7:58 PM, Quinn Stevenson wrote:
> Do we need to keep the “.SNAPSHOT” in the exported package versions?
Does the bnd-maven-plugin feed back the calculated version into the build,
perhaps as a property? We need to inject the correct version number
downstream in the Karaf fe
Arnaud, did you already signed the Apache CLA [1]? I cannot find your
name...
[1] https://www.apache.org/licenses/icla.txt
[2] https://people.apache.org/unlistedclas.html
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member
I think its important to consider that Camel moving to bnd-maven-plugin
will mean most users will do the same, or inherit their projects from a
camel-parent pom or camel-bom. I suggest that end-user Camel projects be
included as a use case, along with the Camel source tree itself.
On 4/5/16 1:
I’ve got the basics down for doing this conversion, but there are a couple of
differences between the MANIFEST.MF files generated by the two tools when
SNAPSHOT versions are used.
Bundle-Version header:
By default, given a version in a POM like "1.2.3-SNAPSHOT”:
- the maven-bundle-plugin conv
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/930
---
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
Seth,
you can create the account yourself. Go to the bottom of a wiki page. There is
an edit-button (red on red). From there you can create your account. When your
ICLA is on file, ask again and someone here will give you karma.
Cheers, Thomas.
-Ursprüngliche Nachricht-
Von: Seth.Soren
GitHub user davgordo opened a pull request:
https://github.com/apache/camel/pull/930
CAMEL-9819: add httpclient to camel-jetty9 test dependencies
The camel-jetty8 component fails to compile for me because of a problem
with a missing dependency, described here:
[CAMEL-9819](https://
Hi,
I've created my account arnaudep...@gmail.com on confluence.
Could you please allow me to edit the documentation ?
By the way, how do you manage the documentation between confluence and
asciidoc ?
Do we have to put special comment in commit and follow some guideline in
confluence ?
Regards
-
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/929
CAMEL-5690 - Using bean component with beans that implement Service from
Camel should have the lifecycle callbacks invoked
You can merge this pull request into a Git repository by running:
Hi Team,
Any response on this ?
in the documentation of camel-SOAP, the example for multipart request &
response states using serviceInterfaceStrategy. however the example is not
clear.
ServiceInterfaceStrategy strat = new
ServiceInterfaceStrategy(com.example.customerservice.multipart.Multi
Please create an account for me to edit the documentation
+1
Tested against some personal POCs here
https://github.com/arnaud-deprez/camel-examples in branch camel-2.16.3
On Tue, Apr 5, 2016 at 7:54 AM Claus Ibsen wrote:
> +1
>
> On Sun, Apr 3, 2016 at 9:27 PM, Gregor Zurowski
> wrote:
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 2.
GitHub user FabianChanton opened a pull request:
https://github.com/apache/camel/pull/928
CAMEL-9815 Add URI parameter to skip declaration of exchange
As described in
[CAMEL-9815](https://issues.apache.org/jira/browse/CAMEL-9815) it could be
helpful to skip the declaration of the e
28 matches
Mail list logo
