There are two outstanding vetoes. Please revert the patch until the
conclusion of this discussion.
Hadrian
On 12/01/2013 03:46 AM, Rob Davies wrote:
dk...@apache.org wrote
Having no way for this PMC to control the display of the Camel route *IS*
a technical justification. If we as a PMC wanted to remove columns, add
new columns for new features, change the order of stuff, etc…. *WE* have
no way to do so.
Having no way to change the branding of what is displayed *IS* a technical
justification. We cannot have links popping up and icons and such that
promote something else.
Having no way to remove all the “cruft” that is unrelated to Camel *IS* a
technical justification. Claus’s screen shot on the wiki has an AcitveMQ
tab, Wiki tab, etc… which would need to be removed if the goal is to have
a Camel route display.
That’s all technical justification. This needs to be removed until they
can all be addressed.
Oh… and the maven goal cannot be camel:hawtio. It would need to be
camel:run-webconsole or similar to remove the branding part from that as
well.
So any 3rd party tool that aids developers, can't be run as a maven target
unless its completely branded and controlled by the Camel PMC is the stance
you are taking.
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-git-commit-CAMEL-7023-Added-hawtio-goal-to-camel-maven-plugin-tp5744029p5744126.html
Sent from the Camel Development mailing list archive at Nabble.com.
