GitHub user hqstevenson opened a pull request:
https://github.com/apache/camel/pull/742
CAMEL-9416 - Creation of camel-mllp component
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hqstevenson/camel CAMEL-9416
Alternatively you
Also another benefit of doing this via a PR is that you will have commits
listed here https://github.com/apache/camel/graphs/contributors :-)
On Mon, Dec 21, 2015 at 1:59 PM, Jon Anstey wrote:
> Hey guys,
>
> If everything is ready, a PR based off master [1] would be nicer for the
> reviewer rat
Hey guys,
If everything is ready, a PR based off master [1] would be nicer for the
reviewer rather than copying in code manually from hqstevenson/camel-mllp.
We mention GitHub PRs here https://camel.apache.org/contributing.html
Thanks!
Jon
[1] https://github.com/apache/camel/tree/master
On Mon,
Oops, wrong Jira:
https://issues.apache.org/jira/browse/CAMEL-9416
On Mon, Dec 21, 2015 at 12:39 PM, Jamie G. wrote:
> Hi All,
>
> We've opened Camel-5296 Adding camel-mlll component to Apache Camel's Jira:
>
> https://issues.apache.org/jira/browse/CAMEL-5296
>
> Quinn and I believe we have the c
Hi All,
We've opened Camel-5296 Adding camel-mlll component to Apache Camel's Jira:
https://issues.apache.org/jira/browse/CAMEL-5296
Quinn and I believe we have the code to the point that's it time to
have the community review and upon acceptance merge into the Camel
2.17.x (master) branch.
Ple
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/741
---
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 gautric opened a pull request:
https://github.com/apache/camel/pull/741
CAMEL-9438 - Unable to use camel-example-cxf
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gautric/camel CAMEL-9438
Alternatively you can revi
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/717
---
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/740
---
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 lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/740
[CAMEL-9437] Fix checkstyle indentation violation for generated API test
cases
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/a
Hi Claus,
I have been looking at doing something similar on the Fuse Jenkins
(see camel-2.15.0.redhat-6-3-x-checkin-incremental and ENTESB-4481) for our
next release as the newer versions of Jenkins support incremental builds.
I haven't spent a lot of time on it yet but so far it looks like most C
11 matches
Mail list logo