Hi,
Sorry for nagging but I haven't received any feedback so far. Is the patch in
the JIRA task ok or is there something wrong with it?
Best regards
Stephan
-Original Message-
From: Siano, Stephan [mailto:stephan.si...@sap.com]
Sent: Montag, 2. November 2015 17:00
To: dev@camel.apache.
Hello,
Any thoughts or comments on this ?
As I wrote above the two code bases has diverged but since the latest
official release has been made from the google code repo I think it would
be best to treat this as the official repository and recreate the gihub
repo with a new import to from google
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/668
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/674
---
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
Dan
> On Nov 7, 2015, at 2:52 PM, Gregor Zurowski wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.14.4 that has 18 fixes and
> improvements. This will be the last official patch release for the
> 2.14.x branch.
>
> Release notes:
> https://issues.apache.org/jira/se
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/675
CAMEL-9307: Remove unnecessary call to setCamelContext when adding a â¦
â¦component by name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
GitHub user nstuart opened a pull request:
https://github.com/apache/camel/pull/674
CAMEL-9161 Change for dealing with parent contexts
Changes to look at current status instead of just checking for parent
context. Using spring cloud automatically adds a parent context which
complet
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/673
CAMEL-9305: PropertiesComponent.isDefaultCreated method only check thâ¦
â¦e absence of defined locations
The method now returns 'false' except but for the default properties
component
No. The order of calling those allow and deny methods is significant.
See http://x-stream.github.io/security.html#framework
> The sequence of registration is essential. The most recently registered
> permission will be evaluated first.
And the two test cases in my original patch file demonstrate
