Github user SvenNold closed the pull request at:
https://github.com/apache/camel/pull/91
---
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 enab
The Apache Jenkins build system has built Camel.2.14.x.notest (build #179)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/179/
to view the results.
Anyone who wants to take the lead here?
Best,
Christian
Am 19.07.2015 10:03 schrieb "Claus Ibsen" :
> Hi
>
> Also as we have similar projects at ASF such as ActiveMQ, Karaf, CXF,
> ServiceMix etc I wonder if there can be some base docker images we can
> extend from or even use the same?
>
> Also
Github user bpeters09 closed the pull request at:
https://github.com/apache/camel/pull/540
---
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 en
Github user davidkarlsen closed the pull request at:
https://github.com/apache/camel/pull/383
---
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 rbudzko closed the pull request at:
https://github.com/apache/camel/pull/566
---
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 enab
Hi
Also as we have similar projects at ASF such as ActiveMQ, Karaf, CXF,
ServiceMix etc I wonder if there can be some base docker images we can
extend from or even use the same?
Also we could have a pre-setup vagrant image as well, as those are
also easy to use.
And if the docker image / vagrant
On Sat, Jul 18, 2015 at 4:37 PM, Willem Jiang wrote:
> There are some private setting of maven setting.xml and pgp private key for
> the releasing.
>
> If we can keep them out side of docker image, it should be OK to push the
> docker image into a public place.
>
> But for my experience, having