[
https://issues.apache.org/jira/browse/CAMEL-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13835649#comment-13835649
]
Babak Vahdat commented on CAMEL-7023:
-------------------------------------
The option "--join" has been introduced *after* hawtio 1.2:
https://github.com/hawtio/hawtio/issues/785
So while trying this with {{camel-example-spring}} I end up with:
{code}
[INFO] Starting hawtio ...
Error: Unknown option: --join
hawtio takes the following options
-h or --help = Displays the help screen
-w or --war = War file or directory of the hawtio web application
-l or --warLocation = Director to search for .war files
-c or --contextPath = Context path
-p or --port = Port number
-ecp or --extraClassPath = Extra classpath
{code}
So I think this should be fixed in {{HawtioMojo}}. Indeed I removed that join
option call and built again. Now when running {{mvn camel:hawtio}} then one can
see from the console output the following log:
{code}
Joining the Jetty server thread
{code}
As apparently the default behaviour by hawtio 1.2 seems to be to join the Jetty
server thread which seems to be not a good default, as because if you then
point your browser to http://localhost:8080/hawtio ... there's not much
displayed (see the attachment).
A new hawtio 1.2.1 release or a hawtio-1.3-M1 release cut could probably fix
this.
> Add hawtio goal to camel plugin
> -------------------------------
>
> Key: CAMEL-7023
> URL: https://issues.apache.org/jira/browse/CAMEL-7023
> Project: Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.12.3, 2.13.0
>
> Attachments: camel-routes.png, camel-tree.png
>
>
> This allows end users to start Camel applications and examples as they would
> do with mvn camel:run, but using mvn camel:hawtio instead, it also bootup the
> hawtio web console.
> This allows end users to use the console to see what happens, visualize the
> Camel routes, debug the routes, profile the routes, and whatnot.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
