Hi Everyone:
This is a vote to release Apache Camel 2.16.1 that has over 60 fixes
and improvements.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12333749
Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-104
Good day,
If I would like to develop a plugin for Camel and would like to see it a
part of FUSE, do I need to consider making it an OSGi bundle myself? What is
the procedure?
Thank you.
Evgeny
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-FUSE-tp5773883.html
Sent fr
I can take care of the Jenkins jobs tomorrow.
Best,
Christian
Am 13.11.2015 15:14 schrieb "Gregor Zurowski" :
> @Claus: Not a problem, I originally planned to start in around 3
> hours. I will wait until you're done with your changes.
>
> @Aki: It seems these build jobs were not set up for the c
So now the repository should be back "online".
I did a reimport of the google code repository and then rebased the changes
in master, that was previously only in the github repo, on top of that.
Hopefully I have not missed any commits.
I had to disable the wmq (and the cis was disabled since befo
Github user davidwilliams1978 closed the pull request at:
https://github.com/apache/camel/pull/682
---
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 featu
Okay sounds good. Will hold of any commits now.
We also got all those tiny PRs in there that people have recently submitted.
On Fri, Nov 13, 2015 at 5:48 PM, Gregor Zurowski
wrote:
> I see CAMEL-9311 was applied to branch camel-2.16.x in the meantime.
> I'd start building the release now.
>
>
>
I see CAMEL-9311 was applied to branch camel-2.16.x in the meantime.
I'd start building the release now.
On Fri, Nov 13, 2015 at 4:16 PM, Claus Ibsen wrote:
> The xstream changes are in. But it would be good to get this backported
> https://issues.apache.org/jira/browse/CAMEL-9311
>
>
>
> On Fri
Github user astefanutti closed the pull request at:
https://github.com/apache/camel/pull/673
---
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
Github user astefanutti closed the pull request at:
https://github.com/apache/camel/pull/679
---
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
Github user astefanutti closed the pull request at:
https://github.com/apache/camel/pull/681
---
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
GitHub user davidwilliams1978 opened a pull request:
https://github.com/apache/camel/pull/682
CAMEL-8302: Added producer label to skipQueueDeclare flag
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davidwilliams1978/camel CAMEL
Github user davidwilliams1978 closed the pull request at:
https://github.com/apache/camel/pull/676
---
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 featu
OK so the new imported repo was trashed I guess due to some forced push.
I will make a new try to fix this later.
Could you please wait with pushing commits for the time beeing.
// Pontus
On Fri, 13 Nov 2015 at 16:51 Pontus Ullgren wrote:
> Hello.
>
> The camel-extra repo from google code has
Hello.
The camel-extra repo from google code has been reimported to a new repo on
github.
The previous import has been renamed to camel-extra-firstimport but I could
not find any easy way to make it read only.
What is left is to reapply the patches I will get onto that during the
weekend.
Best r
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/681
camel-test-blueprint dependency is not required by the Camel Maven plâ¦
â¦ugin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/c
The xstream changes are in. But it would be good to get this backported
https://issues.apache.org/jira/browse/CAMEL-9311
On Fri, Nov 13, 2015 at 3:13 PM, Gregor Zurowski
wrote:
> @Claus: Not a problem, I originally planned to start in around 3
> hours. I will wait until you're done with your c
Github user astefanutti closed the pull request at:
https://github.com/apache/camel/pull/680
---
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
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/680
CAMEL-9321: Blueprint example and archetype does not work when executâ¦
â¦ed with camel:run
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
@Claus: Not a problem, I originally planned to start in around 3
hours. I will wait until you're done with your changes.
@Aki: It seems these build jobs were not set up for the camel-2.16.x
branch. Not sure who has the necessary privileges to configure these
jobs?
On Fri, Nov 13, 2015 at 2:50
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/679
Better resolution of CDI / Blueprint and plugin transitive dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel
ca
Hi
There is a few improvements I currently work on the xstream dsl to
make it easier to setup the new stuff from Java DSL that was omitted.
I will get this sorted within the hour.
On Fri, Nov 13, 2015 at 9:26 AM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> I plan to build the Camel 2.16.1 release
I just noticed that I don't see the 2.16.x jenkins job where i thought
i could find it along with the trunk and 2.15.x jobs.
Is is somewhere else?
2015-11-13 9:26 GMT+01:00 Gregor Zurowski :
> Hi Everyone:
>
> I plan to build the Camel 2.16.1 release later today. Please let me
> know if you stil
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/678
[CAMEL-9320] Cannot set XStream permissions on a per CamelContext basis
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-932
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/677
[CAMEL-9320] Cannot set XStream permissions on a per CamelContext basis
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-932
Hi Gregor,
Ok for me.
Thank you :-)
--
Andrea Cosentino
-
Apache Camel PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, November 13, 2015 9:27 AM, Gregor Zurowski
wrote:
Hi Everyone:
I plan to build the Camel 2.16.1
They told me they are okay.
On Fri, Nov 13, 2015 at 9:54 AM, Gregor Zurowski
wrote:
> Alright, not a problem. I will definitely wait for their feedback
> before starting the release process.
>
> Gregor
>
> On Fri, Nov 13, 2015 at 9:42 AM, Claus Ibsen wrote:
>> Hi
>>
>> The wildfly-camel team
Alright, not a problem. I will definitely wait for their feedback
before starting the release process.
Gregor
On Fri, Nov 13, 2015 at 9:42 AM, Claus Ibsen wrote:
> Hi
>
> The wildfly-camel team will verify the 2.16-SNAPSHOT on their end - it
> takes 1-2h. But it would be good to have their feed
Hi
The wildfly-camel team will verify the 2.16-SNAPSHOT on their end - it
takes 1-2h. But it would be good to have their feedback if they can
find any issues or not.
On Fri, Nov 13, 2015 at 9:26 AM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> I plan to build the Camel 2.16.1 release later today.
Hi Gregor,
Ok for me.
I will not push anything on 2.16.x branch :-)
Thank you,
--
Andrea Cosentino
-
Apache Camel PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, November 13, 2015 9:21 AM, Claus Ibsen wrote:
On Fri,
Hi Everyone:
I plan to build the Camel 2.16.1 release later today. Please let me
know if you still have any pending changes for the camel-2.16.x
branch.
Thanks,
Gregor
Hi Souciance,
Thanks for pointing this out. I have fixed the source code references
on the Jetty wiki page.
Thanks,
Gregor
On Wed, Nov 11, 2015 at 5:20 PM, souciance
wrote:
> Hello,
>
> I was looking at the camel-jetty documentation here:
> https://cwiki.apache.org/confluence/display/CAMEL/Je
On Fri, Nov 13, 2015 at 9:07 AM, Gregor Zurowski
wrote:
> Hi,
>
> I see that CAMEL-9297 is resolved and the fix is also on branch
> camel-2.16.x. Are we good to go for the release now?
>
Yeah I think so. Would you post to @dev a new mail with a email title
about Camel 2.16.1 so its easier for ot
Hi,
I see that CAMEL-9297 is resolved and the fix is also on branch
camel-2.16.x. Are we good to go for the release now?
Thanks,
Gregor
On Tue, Nov 10, 2015 at 8:07 AM, Claus Ibsen wrote:
> Hi
>
> There is a ticket we would like to get in the 2.16.1 release.
> https://issues.apache.org/jira/b
33 matches
Mail list logo
