Hi Cameleers,
this sounds like a good plan to me, I hope to set aside some time to
work on the website and fix outstanding issues and also work on new
functionality in Salesforce component.
zoran
On Thu, Oct 12, 2017 at 1:04 PM, Claus Ibsen wrote:
> Hi
>
> Now that Camel 2.20 is released, then I
Github user PascalSchumacher closed the pull request at:
https://github.com/apache/camel/pull/2027
---
GitHub user MelissaFlinn opened a pull request:
https://github.com/apache/camel/pull/2033
fuse-doc-2017 updated links to box.com
Hi - I'm contributing a fix to the ASCII-doc documentation.
I replaced each box.com link with the appropriate
https://developer.box.com/referenc
Hi
Its fine with 1 JIRA as its in the same component and its about
improving stuff. Its more if its a mix of bug fix and new stuff, then
its good to have more separated as you can then easier backport a bug
fix if its different JIRA tickets and commits.
You can always from a JIRA create sub-tasks
Forgive me if this is a stupid question, but I’m a new committer and wanted to
ask a couple of questions before I started adding some fixes and enhancements
to the camel-mllp component.
1) Should I create a JIRA for each enhancement/fix? Or should I create one
JIRA for all of them (I think th
Hi
Camel 2.21 is intended for start of 2018, hopefully January.
On Thu, Oct 12, 2017 at 5:21 PM, Quinn Stevenson
wrote:
> Do you have a timeframe in mind for 2.21? I already missed 2.20, and I have
> a bunch of updates and enhancements for camel-mllp that I’ve developed on a
> private for whi
Do you have a timeframe in mind for 2.21? I already missed 2.20, and I have a
bunch of updates and enhancements for camel-mllp that I’ve developed on a
private for while working with a customer. I’d like to get the
updates/enhancements included with the next release, but I’m not sure if I’ll
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/2026
---
Hi Claus,
It has come out due to private method
`populateExchangeWithBreadcrumbFromMessageContext`
used in SpringWebserviceConsumer.
I would not prefer depending on servlet API, has not got around with better
option to resolve http transport headers. other option would perhaps be
depending axiom.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/2030
---
Github user onders86 closed the pull request at:
https://github.com/apache/camel/pull/2028
---
Hi Onder
I wonder if this is correct, does spring-ws have any mandatory
dependency on the servlet API?
With this commit there is suddenly a hardcoded dependency on http
servlet, maybe this is wrong.
On Thu, Oct 12, 2017 at 3:36 PM, wrote:
> Repository: camel
> Updated Branches:
> refs/heads/
Hi
Now that Camel 2.20 is released, then I think it would be good to put
out some overall goal of what we among others can/should work on for
the remainder of 2017 in terms of Apache Camel and the next release.
The next release is Apache Camel 2.21 which IMHO should provide these
bigger goals
1)
GitHub user BruceKuiLiu opened a pull request:
https://github.com/apache/camel/pull/2032
Remove the useless condition.
The two conditional expressions always return true in their current control
flow.
They are useless.
You can merge this pull request into a Git repository by ru
GitHub user BruceKuiLiu opened a pull request:
https://github.com/apache/camel/pull/2031
Add the "final" modifier to a public static field.
This static field public but not final, and could be changed by malicious
code or by accident from another package. The field could be made fin
GitHub user richardgroote opened a pull request:
https://github.com/apache/camel/pull/2030
CAMEL-11898: Attachment are not in the response
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/richardgroote/camel patch-2
Alternatively
GitHub user BruceKuiLiu opened a pull request:
https://github.com/apache/camel/pull/2029
Fix the problem of instanceof test always return true.
If these variables are not null, their instanceof test always return true.
They may be failed to be initialized, it would be better to d
Github user frouleau closed the pull request at:
https://github.com/apache/camel/pull/2022
---
Github user vrlgohel closed the pull request at:
https://github.com/apache/camel/pull/1981
---
Github user BruceKuiLiu closed the pull request at:
https://github.com/apache/camel/pull/2025
---
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/2028
CAMEL-11892 - breadcrumbId class cast failure if other than SAAJ usedâ¦
⦠as WebServiceMessage impl
You can merge this pull request into a Git repository by running:
$ git pull https://gith
21 matches
Mail list logo
