Actually, funny you should ask. The camel:dot goal (DotMojo.java) has
not been maintained for 5+ years, is not used and produces output of
very poor quality.
We agreed to remove the camel console from the camel distro and RedHat
intends, I assume, to promote the hawtio solution. Other parties may
promote their own. That should happen outside the Apache Camel project.
I think that was Dan's point, which I consider valid. Please feel free
to create a maven-hawtio-plugin with whatever goodies you deem useful.
Here's a -1 from me too [1]. And a +1 to removing the DotMojo. I will
start a separate thread proposing to remove it.
Hadrian
[1] http://www.apache.org/foundation/voting.html#Veto
On 11/28/2013 08:42 AM, James Strachan wrote:
Should we back out the use of graphviz too? Do you think generating images
for camel routes should be -1'd too?
On 28 November 2013 13:41, James Strachan <james.strac...@gmail.com> wrote:
On 28 November 2013 13:32, Daniel Kulp <dk...@apache.org> wrote:
I’m -1 to this commit. I don’t think we should be adding a bunch of
targets for all the various container/platform integrations.
If that were true I'd maybe -1 it too; but this commit looks to be about
making it easy for Camel users to visualise & debug Camel routes in a web
browser - from inside their existing maven camel project. i.e. its a camel
thing; just needs a web server to host some static HTML/CSS/JS (which is
purely an implementation detail).
Though its nothing really to do with mimicking runtime platforms like
tomcat:run / karaf:run / jetty:run.
--
James
-------
Red Hat
Email: jstra...@redhat.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Open Source Integration
