Re: [wildfly-dev] Generate WildFly BOMs as part of WildFly build

OK, so we need both independence and quick/easy/automated way to used the same versions in BOMs as in wf component matrix. To keep the wf boms independent of wf component matrix we would probably need explicitely defined versions in BOMs + bom-generator similar to https://github.com/wildfly/wildfly-component-matrix-plugin which consumes wf component matrix when needed. Rostislav On Thu, May 17, 2018 at 4:41 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: > > Possible approaches: > > 1) wildfly/boms project could consume the component matrix versions > without any required interaction besides just declaring version of WildFly > component matrix and then building wildfly/boms > > keep in mind that having wildfly/boms seperate from wildfly main release > lifecycle is and welcome addition. > Quickstarts depend solely on boms, and as such should be avalible before > WildFly server release is done, so QS can be developed and tested (also on > OpenShift) > > -- > tomaz > > > On Tue, May 15, 2018 at 1:28 PM, Rostislav Svoboda <rsvoboda(a)redhat.com&gt; > wrote: > >> Hi team. >> >> WildFly and WildFly core generate component-matrix as part of the build >> now. >> https://issues.jboss.org/browse/WFLY-10365 >> >> We should also consider automated propagation of current WildFly master >> component versions into WildFly BOMs - https://github.com/wildfly/boms. >> I'm especially interested in >> https://github.com/wildfly/boms/tree/master/client >> Currently, the sync is rather complicated (manual) and not at all >> intuitive to implement. >> Tomaz did great job on BOMs but with his departure nothing is really >> happening in this area. >> >> Possible approaches: >> 1) wildfly/boms project could consume the component matrix versions >> without any required interaction besides just declaring version of WildFly >> component matrix and then building wildfly/boms >> >> 2) generating -SNAPSHOT versions of WildFly BOMs as part of WildFly >> build (going back I know) ++ publishing just the final BOMs to >> https://github.com/wildfly/boms ? >> >> Comments / suggestions ? >> >> Regards. >> Rostislav >> >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> > > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev