Re: [Hawkular-dev] Console project structure and plugins

On 27 Jan 2015, at 09:09, Viliam Rockai <vrockai(a)redhat.com&gt; wrote: Hey All, I want to start this thread to gather some information about how components are shared between projects. So, to make the terminology clear, lets check this stuff: https://github.com/vrockai/hawkular/tree/master/ui/console/alerts https://github.com/vrockai/hawkular/tree/master/ui/console/metrics are future components/widgets which are going to be used on the console page. Those components are Hawtio 2.x plugins. According to: https://github.com/hawtio/hawtio/blob/master/docs/Overview2dotX.md I expect exposing plugins as bower packages is the preferred way in Hawtio 2.x. From my perspective (angular guy) this is pretty much what is expected. The only way to expose/share those components as bower packages to third-parties would be to put them in separate repo. As was already said on IRC, this may be overkill. I see two ways of resolution: 1. Create separate repository for each component. Those all would be bower dependencies of the hawkular console. Pros: possibly consistent with the Hawtio 2.x ways, modularity = we download only what we need. Cons: lots of repositories to take care of. 2. Create a single repository for all the plugins. The whole library of sibling components, similar to i.e. Angular-UI. Pros: easier maintenance. Cons: less modular = need to download whole library before we filter which plugins we want to use.

I see, that the 2nd approach already exists in the hawtio repository, probably the best way would be to put our components to this repo: https://github.com/hawtio/hawtio-ui Thanks for your thoughts, Viliam _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev