Rafael, I can't answer your question, but isn't the stacks.yaml for all released versions? Is there supported only latest greatest combinations? On 08/19/2013 09:50 PM, Rafael Benevides wrote: > Since I'm about to work on new organization and Stacks 1.1 format I'd > like to check with you guys about keeping the WFK 2.1 BOMs on stacks.yaml > > WFK 2.1 BOMs uses a different groupdId (com.redhat.jboss.wfk.boms) > which seems that was used only on WFK 2.1 > > Now that we're moving to org.jboss.bom(eap|wfk|etc) I'd like to > cleanup those WFK 2.1 BOMs and just keep WFK 2.2 and WFK 2.3 BOMs. Is > that something that I could do without causing any impacts ? > > Thanks > -- Marek Novotny -- WFK and Seam Product Lead Red Hat Czech s.r.o. Purkynova 99 612 45 Brno

Yes, not sure why we would remove the old ones. On 20 Aug 2013, at 11:21, Max Rydahl Andersen <manderse(a)redhat.com&gt; wrote: > My understanding was also that stacks.yml would contain all released versions, > but then have markers for which are the recommended ones? > > /max > > On Tue, Aug 20, 2013 at 10:54:56AM +0200, Marek Novotny wrote: >> Rafael, >> >> I can't answer your question, but isn't the stacks.yaml for all >> released versions? Is there supported only latest greatest combinations? >> >> On 08/19/2013 09:50 PM, Rafael Benevides wrote: >>> Since I'm about to work on new organization and Stacks 1.1 format I'd >>> like to check with you guys about keeping the WFK 2.1 BOMs on stacks.yaml >>> >>> WFK 2.1 BOMs uses a different groupdId (com.redhat.jboss.wfk.boms) >>> which seems that was used only on WFK 2.1 >>> >>> Now that we're moving to org.jboss.bom(eap|wfk|etc) I'd like to >>> cleanup those WFK 2.1 BOMs and just keep WFK 2.2 and WFK 2.3 BOMs. Is >>> that something that I could do without causing any impacts ? >>> >>> Thanks >>> >> >> -- >> Marek Novotny >> -- >> WFK and Seam Product Lead >> >> Red Hat Czech s.r.o. >> Purkynova 99 >> 612 45 Brno >>