Re: [Hawkular-dev] Collapsing of Repos ?

Personally I don't see the benefit of collapsing repos. Also, I'm not sure if "collapsing" here means also "merging" in the sense that we move 2 or more components into 1, with only 1 new release of the joined component in the future. I'm +1 to maintain repos by domain, perhaps joining helper repos in commons. But I see more problematic if we join big repos like metrics, alerts or inventory into one. It is clear that they have their own lifecycle and merging can bring more issues than benefits. Having said that, I don't see that having separate repo is a problem to make them work together. For example, from my point of view, a join combination of alerts+metrics is just a packaging option which can be independent of if it is built from one repo or two. Just my 2 cents. ----- Mensaje original ----- > De: "Heiko W.Rupp" <hrupp(a)redhat.com&gt; > Para: "Discussions around Hawkular development" <hawkular-dev(a)lists.jboss.org&gt; > Enviados: Miércoles, 4 de Mayo 2016 16:10:00 > Asunto: [Hawkular-dev] Collapsing of Repos ? > > Hi, > > we do have a larger number of repositories and source trees. > Now that we have narrowed down the scope of our work a bit and also > have an idea of what we need for the "core services" package, I wonder > if we can collapse repositories and source trees into larger ones. > > As an example: alerts and metrics could go together into > hawkular-metrics and the forwarding of data to alerts could be > done with Java method invocation. > > What else could be done here? > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev