On 1 Dec 2013, at 13:25, dk...@apache.org [via Camel] <ml-node+s465427n5744130...@n5.nabble.com> wrote: > > > > > 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. > > If the maven plugin is part of Camel and it’s stated purpose it to present > *Camel* to the user, then yes. That BETTER be under the PMC’s complete > control and influence.
It is neither reasonable or practical to have control over all 3rd party projects/tools. When application of the Apache branding policy is so over zealous that it negates the common good then there is either something seriously wrong with the branding policy or your interpretation of it. ----------------- Red Hat, Inc Twitter: rajdavies Blog: http://rajdavies.blogspot.com ActiveMQ in Action: http://www.manning.com/snyder/ -- View this message in context: http://camel.465427.n5.nabble.com/Re-git-commit-CAMEL-7023-Added-hawtio-goal-to-camel-maven-plugin-tp5744029p5744135.html Sent from the Camel Development mailing list archive at Nabble.com.
