Hi *, There are two new parent releases 36 and 37. Version 36 contains some usual lib and plugin upgrades [1] and should be applicable smoothly in all Hawkular components. I already have some PRs ready. You do not need to do anything unless you need to proceed quickly. Parent 36 should be used in Hawkular 1.0.0.Alpha11. Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed to need adaptations in components, most notably in Inventory. Feel free to start experimenting with Hawkular Parent 37. Cassandra 3.3 was chosen to be the version for OpenShift 3.2. Best, Peter [1] https://github.com/hawkular/hawkular-parent-pom/commits/36 [2] https://github.com/hawkular/hawkular-parent-pom/commits/37 _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

Hi Gary, seeing that you extend the hawkular-accounts-feature-pack, you indeed might consider waiting for the new accounts FP and then remove the files that you copied from hawkular-accounts-feature-pack as made possible by the new FP plugin that is available via Parent 36. I am just doing the same thing in commons. I can show you the result when I it is ready to give you some guidance. -- P On 2016-02-25 17:58, Gary Brown wrote: > Ah :( - just released BTM 0.7.1.Final on parent 35. So I guess I will need > to do another release? > > ----- Original Message ----- >> Hi *, >> >> There are two new parent releases 36 and 37. >> >> Version 36 contains some usual lib and plugin upgrades [1] and should be >> applicable smoothly in all Hawkular components. I already have some PRs >> ready. You do not need to do anything unless you need to proceed quickly. >> Parent 36 should be used in Hawkular 1.0.0.Alpha11. >> >> Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed to >> need adaptations in components, most notably in Inventory. Feel free to >> start experimenting with Hawkular Parent 37. >> >> Cassandra 3.3 was chosen to be the version for OpenShift 3.2. >> >> Best, >> >> Peter >> >> [1] https://github.com/hawkular/hawkular-parent-pom/commits/36 >> [2] https://github.com/hawkular/hawkular-parent-pom/commits/37 >> _______________________________________________ >> 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 > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

Hi Peter, I've done a quick test with latest snapshot of BTM in hawkular master, and the integration feature pack seems to be working fine. Just wanted to confirm there were no other changes you wanted to do before I released BTM?

Regards Gary ----- Original Message ----- > Hi Gary, seeing that you extend the hawkular-accounts-feature-pack, you > indeed might consider waiting for the new accounts FP and then remove > the files that you copied from hawkular-accounts-feature-pack as made > possible by the new FP plugin that is available via Parent 36. I am just > doing the same thing in commons. I can show you the result when I it is > ready to give you some guidance. -- P > > On 2016-02-25 17:58, Gary Brown wrote: >> Ah :( - just released BTM 0.7.1.Final on parent 35. So I guess I will need >> to do another release? >> >> ----- Original Message ----- >>> Hi *, >>> >>> There are two new parent releases 36 and 37. >>> >>> Version 36 contains some usual lib and plugin upgrades [1] and should be >>> applicable smoothly in all Hawkular components. I already have some PRs >>> ready. You do not need to do anything unless you need to proceed quickly. >>> Parent 36 should be used in Hawkular 1.0.0.Alpha11. >>> >>> Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed to >>> need adaptations in components, most notably in Inventory. Feel free to >>> start experimenting with Hawkular Parent 37. >>> >>> Cassandra 3.3 was chosen to be the version for OpenShift 3.2. >>> >>> Best, >>> >>> Peter >>> >>> [1] https://github.com/hawkular/hawkular-parent-pom/commits/36 >>> [2] https://github.com/hawkular/hawkular-parent-pom/commits/37 >>> _______________________________________________ >>> 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 >> > > _______________________________________________ > 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

Spoke too soon - I hadn't set hawkular master to use parent 36, or updated commons/accounts. Currently the artifacts are being put in different locations in the modules folder. Console is not showing up. Any suggestion for how to proceed? Looks like BTM is dependent upon console being updated as well. Regards Gary ----- Original Message ----- > Hi Gary, > > On 2016-03-01 09:34, Gary Brown wrote: > > Hi Peter, > > > > I've done a quick test with latest snapshot of BTM in hawkular master, > > and > > the integration feature pack seems to be working fine. Just wanted to > > confirm there were no other changes you wanted to do before I released > > BTM? > > No, only Parent 36 and the related cosmetics. Feel free to release now. -- > P > > > Regards > > Gary > > > > ----- Original Message ----- > >> Hi Gary, seeing that you extend the hawkular-accounts-feature-pack, you > >> indeed might consider waiting for the new accounts FP and then remove > >> the files that you copied from hawkular-accounts-feature-pack as made > >> possible by the new FP plugin that is available via Parent 36. I am just > >> doing the same thing in commons. I can show you the result when I it is > >> ready to give you some guidance. -- P > >> > >> On 2016-02-25 17:58, Gary Brown wrote: > >>> Ah :( - just released BTM 0.7.1.Final on parent 35. So I guess I will > >>> need > >>> to do another release? > >>> > >>> ----- Original Message ----- > >>>> Hi *, > >>>> > >>>> There are two new parent releases 36 and 37. > >>>> > >>>> Version 36 contains some usual lib and plugin upgrades [1] and should > >>>> be > >>>> applicable smoothly in all Hawkular components. I already have some > >>>> PRs > >>>> ready. You do not need to do anything unless you need to proceed > >>>> quickly. > >>>> Parent 36 should be used in Hawkular 1.0.0.Alpha11. > >>>> > >>>> Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed > >>>> to > >>>> need adaptations in components, most notably in Inventory. Feel free > >>>> to > >>>> start experimenting with Hawkular Parent 37. > >>>> > >>>> Cassandra 3.3 was chosen to be the version for OpenShift 3.2. > >>>> > >>>> Best, > >>>> > >>>> Peter > >>>> > >>>> [1] https://github.com/hawkular/hawkular-parent-pom/commits/36 > >>>> [2] https://github.com/hawkular/hawkular-parent-pom/commits/37 > >>>> _______________________________________________ > >>>> 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 > >>> > >> > >> _______________________________________________ > >> 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 > > > > _______________________________________________ > 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

Hi Gary, where can I see the changes you speak about? -- P On 2016-03-01 11:21, Gary Brown wrote: > Hi Peter > > If all of the artifacts in the modules/org/hawkular...../nest/deployments > folder are moved under modules/system/layers/..., then it worked fine. So > I will change the location of the integrated feature pack (including where > it places the console bits), assuming that these will be relocated once > hawkular is moved to parent 36 etc. > > Regards > Gary > > ----- Original Message ----- >> Spoke too soon - I hadn't set hawkular master to use parent 36, or updated >> commons/accounts. >> >> Currently the artifacts are being put in different locations in the >> modules >> folder. Console is not showing up. >> >> Any suggestion for how to proceed? Looks like BTM is dependent upon >> console >> being updated as well. >> >> Regards >> Gary >> >> ----- Original Message ----- >>> Hi Gary, >>> >>> On 2016-03-01 09:34, Gary Brown wrote: >>>> Hi Peter, >>>> >>>> I've done a quick test with latest snapshot of BTM in hawkular master, >>>> and >>>> the integration feature pack seems to be working fine. Just wanted to >>>> confirm there were no other changes you wanted to do before I released >>>> BTM? >>> >>> No, only Parent 36 and the related cosmetics. Feel free to release now. >>> -- >>> P >>> >>>> Regards >>>> Gary >>>> >>>> ----- Original Message ----- >>>>> Hi Gary, seeing that you extend the hawkular-accounts-feature-pack, you >>>>> indeed might consider waiting for the new accounts FP and then remove >>>>> the files that you copied from hawkular-accounts-feature-pack as made >>>>> possible by the new FP plugin that is available via Parent 36. I am >>>>> just >>>>> doing the same thing in commons. I can show you the result when I it is >>>>> ready to give you some guidance. -- P >>>>> >>>>> On 2016-02-25 17:58, Gary Brown wrote: >>>>>> Ah :( - just released BTM 0.7.1.Final on parent 35. So I guess I will >>>>>> need >>>>>> to do another release? >>>>>> >>>>>> ----- Original Message ----- >>>>>>> Hi *, >>>>>>> >>>>>>> There are two new parent releases 36 and 37. >>>>>>> >>>>>>> Version 36 contains some usual lib and plugin upgrades [1] and should >>>>>>> be >>>>>>> applicable smoothly in all Hawkular components. I already have some >>>>>>> PRs >>>>>>> ready. You do not need to do anything unless you need to proceed >>>>>>> quickly. >>>>>>> Parent 36 should be used in Hawkular 1.0.0.Alpha11. >>>>>>> >>>>>>> Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed >>>>>>> to >>>>>>> need adaptations in components, most notably in Inventory. Feel free >>>>>>> to >>>>>>> start experimenting with Hawkular Parent 37. >>>>>>> >>>>>>> Cassandra 3.3 was chosen to be the version for OpenShift 3.2. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Peter >>>>>>> >>>>>>> [1] https://github.com/hawkular/hawkular-parent-pom/commits/36 >>>>>>> [2] https://github.com/hawkular/hawkular-parent-pom/commits/37 >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> _______________________________________________ >>> 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 >> > _______________________________________________ > 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

> > Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed to > need adaptations in components, most notably in Inventory. Feel free to > start experimenting with Hawkular Parent 37. > > Cassandra 3.3 was chosen to be the version for OpenShift 3.2. > Hawkular Metrics currently does not support C* 3.3 and there are no plans to retroactively update any previous releases to support C* 3.x. I am not sure what is the basis for the information in the last sentence.

Thank you, Stefan Negrea _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

On Mar 1, 2016, at 10:44 AM, Stefan Negrea <snegrea(a)redhat.com&gt; wrote: ----- Original Message ----- > From: "Peter Palaga" <ppalaga(a)redhat.com&gt; > To: "Discussions around Hawkular development" <hawkular-dev(a)lists.jboss.org&gt; > Sent: Tuesday, March 1, 2016 8:38:53 AM > Subject: Re: [Hawkular-dev] Parent releases 36 (usual upgrades) and 37 (Cassandra 3.3) > > Hi Stefan, inline... > > On 2016-03-01 15:05, Stefan Negrea wrote: >> >>> >>> Version 37 upgrades to Cassandra 3.3 and Driver 3.0.0 and is supposed to >>> need adaptations in components, most notably in Inventory. Feel free to >>> start experimenting with Hawkular Parent 37. >>> >>> Cassandra 3.3 was chosen to be the version for OpenShift 3.2. >>> >> >> Hawkular Metrics currently does not support C* 3.3 and there are no plans >> to retroactively update any previous releases to support C* 3.x. I am not >> sure what is the basis for the information in the last sentence. > > Sorry for the confusion, I had improper info about which OpenShift > version is c* 3.3 targeting. Apparently, c* 3.3 targets OpenShift 3.3. This is not accurate either; I am not aware of any final decisions regarding C* upgrades at this time.