Even if there is this cycle, I'm pretty sure hawtio isn't tied to a specific version of camel so it shouldnt be an issue. On 2013-12-01 9:40 AM, "Jon Anstey" <jans...@gmail.com> wrote:
> I think this is the first possible technical issue in this thread... > Although I haven't looked at the dependency graph myself to see if its > actually an issue :-) > > We certainly do not have the requirement to brand and control every 3rd > party tool we interact with. Like, we deploy poms that specify a profile > setup.eclipse. Should we rename it to setup.ide?? I don't mean to be > disrespectful, I'm just suggesting something far fetched to try and prove a > point. > > Cheers, > Jom > On 2013-12-01 6:09 AM, "Christian Schneider" <ch...@die-schneider.net> > wrote: > >> I see another technical issue with the relation between camel and hawtio. >> The Hawtio camel integration depends on camel. If we now add a dependency >> from camel to hawtio this creates a circular depenency that tightly couples >> the projects in a way that should be avoided. >> >> So why not just provide a small camel hawtio plugin inside hawtio that >> does this integration. So the dependency is simply from hawtio to camel. >> For the users this does not make a difference in usability but technically >> it is cleaner. >> >> Christian >> >> Am 01.12.2013 09:46, schrieb Rob Davies: >> >>> 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. >>> >> >> >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> Talend Application Integration Division http://www.talend.com >> >>
