GitHub user tadayosi opened a pull request:
https://github.com/apache/camel/pull/2559
CAMEL-12873: camel-servlet - Example for HttpRegistry no longer worksâ¦
⦠throwing FinalModifierException
It also recovers an example test which existed under
`tests/camel-itest-osgi/sr
lburgazzoli closed pull request #170: runtime(groovy) : improve registry dsl
URL: https://github.com/apache/camel-k/pull/170
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pul
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/2558
---
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/2558
CAMEL-12087: camel-core: WARN No CamelContext defined yet so cannot inject
into bean
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburga
Very nice Riccardo!
Also the kubernetes explorer may turn out to be useful in the future once
we start working on Knative integration (that is completely based on custom
CRDs).
I've added a high level goal for the UI, together with others in
https://github.com/apache/camel-k/projects, so we can tr
This task is really interesting. It seems a good one to work together on :-)
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, October 9,
> On 9 Oct 2018, at 13:56, Riccardo Forina wrote:
>
> Hi Antonin,
>
> absolutely! I actually thought about doing it like that at first, but
> then decided to have a client-only solution for this POC.
> I guess deciding how to implement this will depend on how we want to
> make this UI availabl
Hi Antonin,
absolutely! I actually thought about doing it like that at first, but
then decided to have a client-only solution for this POC.
I guess deciding how to implement this will depend on how we want to
make this UI available. Something like `kamel ui` to spin a web
server perhaps? Maybe wit
That sounds great indeed !
Gonna take a deeper look asap.
Regards
JB
Le 9 oct. 2018 à 13:41, à 13:41, Antonin Stefanutti a
écrit:
>Hi Riccardo,
>
>This looks very promising! I think having a Web UI for Camel-K would be
>very valuable.
>
>Here are my quick feedback:
>- It’d be great to have the
Hi Riccardo,
This looks very promising! I think having a Web UI for Camel-K would be very
valuable.
Here are my quick feedback:
- It’d be great to have the UI self-hosted. For it to work while avoiding to
configure CORS on the API server, it is possible to proxy the communication to
the API se
astefanutti commented on issue #77: Need a Web UI?
URL: https://github.com/apache/camel-k/issues/77#issuecomment-428138813
`camel-k-ui` looks very promising! Let me close this issue, which was more
of a question, and iterate there.
--
astefanutti closed issue #77: Need a Web UI?
URL: https://github.com/apache/camel-k/issues/77
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to
lburgazzoli opened a new issue #169: Investigate switching to kubebuilder
URL: https://github.com/apache/camel-k/issues/169
https://github.com/kubernetes-sigs/kubebuilder
This is an automated message from the Apache Git Servic
nicolaferraro opened a new issue #168: Publish Helm charts
URL: https://github.com/apache/camel-k/issues/168
Depends on #167.
We should decide how and where we publish helm charts so that people can
reference them.
Thi
nicolaferraro opened a new issue #167: Package installation artifacts with Helm
URL: https://github.com/apache/camel-k/issues/167
The `kamel` binary is useful for development purposes, but we need also to
be compatible with CI/CD platforms to support automated deployments.
First targ
lburgazzoli commented on issue #77: Need a Web UI?
URL: https://github.com/apache/camel-k/issues/77#issuecomment-428105930
FYI:
https://lists.apache.org/thread.html/2b88a717a41468686cb542f75a25fbaea10da288e9423925f12fb392@%3Cdev.camel.apache.org%3E
--
oscerd closed issue #161: kamel "get" should not return contexts
URL: https://github.com/apache/camel-k/issues/161
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and
oscerd closed pull request #166: Regenerate code, deps and fixes
URL: https://github.com/apache/camel-k/pull/166
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (f
lburgazzoli opened a new pull request #166: Regenerate code, deps and fixes
URL: https://github.com/apache/camel-k/pull/166
Fixes #161
This is an automated message from the Apache Git Service.
To respond to the message, please
nicolaferraro commented on issue #161: kamel "get" should not return contexts
URL: https://github.com/apache/camel-k/issues/161#issuecomment-428101848
Ahaha.. I didn't notice it was correct :smile:
This is an automated messag
lburgazzoli commented on issue #161: kamel "get" should not return contexts
URL: https://github.com/apache/camel-k/issues/161#issuecomment-428101347
This is correct, the last line should be read as:
| NAME | CONTEXT | STATUS |
|:-|:-:|:-|
| withrest | ct
This is wonderful, thanks a lot!
I'll have a deeper look today.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, October 9, 2018, 9:15:
Hello everybody,
in the last few days, I have been working on a GUI for camel-k, for a few
reasons:
- I know nothing about Camel, so this seemed a good way to test the water
- Nicola asked me if I could do it :D
The main, and only, goal was to edit a custom resource and save it. Since to do
th
23 matches
Mail list logo
