You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/01/21 09:32:58 UTC
[GitHub] [camel-quarkus] ppalaga opened a new issue #2156: Consider supporting Quarkus Dev UI in our extensions
ppalaga opened a new issue #2156:
URL: https://github.com/apache/camel-quarkus/issues/2156
Since Quarkus 1.11.0.Final, there is Quarkus Dev UI, see https://quarkus.io/guides/dev-ui
It allows to quickly visualise all the extensions currently loaded, see their status and go directly to their documentation.
The good news is that the docs links work for Camel Quarkus extensions.
On top of that, each extension can add:
* [Custom useful bits of runtime information in the overview](https://quarkus.io/guides/dev-ui#how-can-i-make-my-extension-support-the-dev-console)
* [Full custom pages](https://quarkus.io/guides/dev-ui#adding-full-pages)
* [Interactive pages with actions](https://quarkus.io/guides/dev-ui#advanced-usage-adding-actions)
I wonder which of the above should we support?
See also https://github.com/quarkusio/quarkus/issues/14471
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2156: Consider supporting Quarkus Dev UI in our extensions
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2156:
URL: https://github.com/apache/camel-quarkus/issues/2156#issuecomment-771819809
To hide an extension from the Dev console, it should be enough to remove the docs link from the metadata. We should consider doing it for at least those support extensions which expose no Quarkus configuration.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] davsclaus commented on issue #2156: Consider supporting Quarkus Dev UI in our extensions
Posted by GitBox <gi...@apache.org>.
davsclaus commented on issue #2156:
URL: https://github.com/apache/camel-quarkus/issues/2156#issuecomment-1033619169
Camel 3.15 comes with API for developer console (camel-console JAR).
It is an early prototype that comes with a set of out of the box consoles to provide various information about your running Camel application. More consoles will be added.
These consoles currently are text based, but we need to spec the data in JSon so graphical consoles in camel-quarkus can use the data and display nicely.
It seems the website has not updated yet with camel 3.15 docs, but there are some early details here
https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/camel-console.adoc
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] zbendhiba commented on issue #2156: Consider supporting Quarkus Dev UI in our extensions
Posted by GitBox <gi...@apache.org>.
zbendhiba commented on issue #2156:
URL: https://github.com/apache/camel-quarkus/issues/2156#issuecomment-1033608998
There are 2 interesting ideas I have, but there are just ideas from a non frontend person, and I don't know if those are easy to tackle:
- Looking at this kind of Dev UI developed recently : https://github.com/quarkusio/quarkus/issues/21059
- Or go for a more common UI around Camel projects, and have a dedicated back-end for Quarkus Dev UI. As for Kogito's demo on [Quarkus insights](https://youtu.be/efPuzK2YM4I). This idea is kind of a way bigger project.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2156: Consider supporting Quarkus Dev UI in our extensions
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2156:
URL: https://github.com/apache/camel-quarkus/issues/2156#issuecomment-771819809
To hide an extension from the Dev console, it should be enough to remove the docs link from the metadata. We should consider doing it for at least those support extensions which expose no Quarkus configuration.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org