Accounts tracking JIRA: HAWKULAR-362 I'll perform the changes in Accounts' dist, which can later be used as base for the main Hawkular dist. - Juca. On 06/17/2015 09:08 AM, Thomas Heute wrote: > We have to upgrade to WF9 to get more data out of WF9. > there are quite some changes to be made: - Parent declares the > version of WF to use and BOM: here is my branch: > https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 > - Accounts need to upgrade to KC 1.3 (to be released this week) > Juca will work on this - Bus/Nest needs to adapt here is my > branch https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 > (needs another patch from Mazz) - Agent also needs some changes. > WF 9 GA is supposed to go out at any point now, let's try to > coordinate around that, if you have a release pending, think of > that. > BTW, I tried to reflect the dependencies between component, > would have been easier if everyone could respect our standards, > in particular: - declare all dependencies at the root pom - use > <version./groupid/> in pom properties. So please fix this if you > do not follow those basic rules. > PS: for the upstream project, it is ok if all dependencies don't > fully align, for instance 2 components could depend on 2 > different versions of the parent. > Thomas > _______________________________________________ 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

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVgUIAAAoJECKM1e+fkPrXLUgH/jpV7wTTlayfAY5FVzRBJdA5 AyELpcT9KSQlrVntMKwi6fi8nNWLRzTXR06XP8mLrSVW8w6/fImxICxpi6/ztKhP zrJ7rh7yU2bsdLFOKm9amfSwF4aW/ypS5Hvc7CXqwI1zR6S/3hqXAanqkRQcn5Db G244XgypyuSKeURQ5/64XWrWE9TeaJykHTtwWWh7GWVxACGlamWjLSLKp0G2k/Qr cxkcf3LRohM82H9vo6/RRk3RnrOhzpnyOBxM9uVg787f0FVIgYEpdv/ahDTUMc96 C64dYabq7qHMKgJxPnl67DkEwBREc+LVvFlCMGkkBRiYvMMyTau6MSCXblGbX4Q= =dvQq -----END PGP SIGNATURE-----

For now updating and fixing. We should look into feature packs stuff and if that helps separately Thomas On 06/17/2015 11:46 AM, Juraci Paixão Kröhling wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > By the way: does this task means that we are building feature packs > for WF9, or we are just bumping the WF version and fixing whatever > breaks? > > - - Juca. > > On 06/17/2015 11:45 AM, Juraci Paixão Kröhling wrote: >> Accounts tracking JIRA: HAWKULAR-362 >> >> I'll perform the changes in Accounts' dist, which can later be used >> as base for the main Hawkular dist. >> >> - Juca. >> >> On 06/17/2015 09:08 AM, Thomas Heute wrote: >> >>> We have to upgrade to WF9 to get more data out of WF9. >> >>> there are quite some changes to be made: - Parent declares the >>> version of WF to use and BOM: here is my branch: >>> https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 >>> - Accounts need to upgrade to KC 1.3 (to be released this week) >>> Juca will work on this - Bus/Nest needs to adapt here is my >>> branch https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 >>> (needs another patch from Mazz) - Agent also needs some changes. >> >>> WF 9 GA is supposed to go out at any point now, let's try to >>> coordinate around that, if you have a release pending, think of >>> that. >> >>> BTW, I tried to reflect the dependencies between component, >>> would have been easier if everyone could respect our standards, >>> in particular: - declare all dependencies at the root pom - use >>> <version./groupid/> in pom properties. So please fix this if you >>> do not follow those basic rules. >> >>> PS: for the upstream project, it is ok if all dependencies don't >>> fully align, for instance 2 components could depend on 2 >>> different versions of the parent. >> >>> Thomas >> >> >>> _______________________________________________ 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

FWIW: I also have a separate branch where the agent is built and can be run in WildFly Swarm - but it won't work until we move to WF9. So once we go to WF9, I'll introduce this agent swarm stuff as well. ----- Original Message ----- > > We have to upgrade to WF9 to get more data out of WF9. > > there are quite some changes to be made: > - Parent declares the version of WF to use and BOM: > here is my branch: > https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 > - Accounts need to upgrade to KC 1.3 (to be released this week) > Juca will work on this > - Bus/Nest needs to adapt > here is my branch > https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs another > patch from Mazz) > - Agent also needs some changes. > > WF 9 GA is supposed to go out at any point now, let's try to coordinate > around that, if you have a release pending, think of that. > > BTW, I tried to reflect the dependencies between component, would have > been easier if everyone could respect our standards, in particular: > - declare all dependencies at the root pom > - use <version./groupid/> in pom properties. > So please fix this if you do not follow those basic rules. > > PS: for the upstream project, it is ok if all dependencies don't fully > align, for instance 2 components could depend on 2 different versions of > the parent. > > Thomas > > _______________________________________________ > 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

then we should close https://issues.jboss.org/browse/HAWKULAR-192 - because it was that JIRA that caused me to even look at swarm. ----- Original Message ----- > As said before, we can't use/rely on Swarm, so -1 to put that in our build. > This won't be supported, Swarm is a R&P project while Hawkular is a R&D > project > > Thomas > > On 06/17/2015 03:18 PM, John Mazzitelli wrote: >> FWIW: I also have a separate branch where the agent is built and can be run >> in WildFly Swarm - but it won't work until we move to WF9. So once we go >> to WF9, I'll introduce this agent swarm stuff as well. >> >> ----- Original Message ----- >>> >>> We have to upgrade to WF9 to get more data out of WF9. >>> >>> there are quite some changes to be made: >>> - Parent declares the version of WF to use and BOM: >>> here is my branch: >>> https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 >>> - Accounts need to upgrade to KC 1.3 (to be released this week) >>> Juca will work on this >>> - Bus/Nest needs to adapt >>> here is my branch >>> https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs another >>> patch from Mazz) >>> - Agent also needs some changes. >>> >>> WF 9 GA is supposed to go out at any point now, let's try to coordinate >>> around that, if you have a release pending, think of that. >>> >>> BTW, I tried to reflect the dependencies between component, would have >>> been easier if everyone could respect our standards, in particular: >>> - declare all dependencies at the root pom >>> - use <version./groupid/> in pom properties. >>> So please fix this if you do not follow those basic rules. >>> >>> PS: for the upstream project, it is ok if all dependencies don't fully >>> align, for instance 2 components could depend on 2 different versions of >>> the parent. >>> >>> Thomas >>> >>> _______________________________________________ >>> 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

Regarding the fact that we need to upgrade to WF9 to get more data from it.. does it means that Hawkular will only be "compatible" with WF9+ ? Because for instance, I'm thinking on the Web Metrics screen, with WF8 we can't (in a very sane way) get the data we need to fill it as we will be able with WF9. So it will work fine with the local server, since it will be WF9, but what if a WF8 server is added to be monitored, how do we display that same data ? Do we need server type specific screens ? This should also apply to other metrics screens regarding other server types (that we might support in the future). Alexandre ----- Original Message ----- From: "Thomas Heute" <theute(a)redhat.com&gt; To: "Discussions around Hawkular development" <hawkular-dev(a)lists.jboss.org&gt; Sent: Wednesday, 17 June, 2015 8:08:19 AM Subject: [Hawkular-dev] WF 9 upgrade We have to upgrade to WF9 to get more data out of WF9. there are quite some changes to be made: - Parent declares the version of WF to use and BOM: here is my branch: https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 - Accounts need to upgrade to KC 1.3 (to be released this week) Juca will work on this - Bus/Nest needs to adapt here is my branch https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs another patch from Mazz) - Agent also needs some changes. WF 9 GA is supposed to go out at any point now, let's try to coordinate around that, if you have a release pending, think of that. BTW, I tried to reflect the dependencies between component, would have been easier if everyone could respect our standards, in particular: - declare all dependencies at the root pom - use <version./groupid/> in pom properties. So please fix this if you do not follow those basic rules. PS: for the upstream project, it is ok if all dependencies don't fully align, for instance 2 components could depend on 2 different versions of the parent. Thomas _______________________________________________ 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-parent 16 with an upgrade to WF9 was just released and I have sent PRs to all projects on my list. -- P On 17/06/15 09:08, Thomas Heute wrote: > > We have to upgrade to WF9 to get more data out of WF9. > > there are quite some changes to be made: > - Parent declares the version of WF to use and BOM: > here is my branch: > https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 > - Accounts need to upgrade to KC 1.3 (to be released this week) > Juca will work on this > - Bus/Nest needs to adapt > here is my branch > https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs another > patch from Mazz) > - Agent also needs some changes. > > WF 9 GA is supposed to go out at any point now, let's try to coordinate > around that, if you have a release pending, think of that. > > BTW, I tried to reflect the dependencies between component, would have > been easier if everyone could respect our standards, in particular: > - declare all dependencies at the root pom > - use <version./groupid/> in pom properties. > So please fix this if you do not follow those basic rules. > > PS: for the upstream project, it is ok if all dependencies don't fully > align, for instance 2 components could depend on 2 different versions of > the parent. > > Thomas > > > _______________________________________________ > 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

https://issues.jboss.org/browse/HWKMETRICS-145 On 06/19/2015 01:22 PM, Thomas Segismont wrote: > Can you close your PR against Metrics and open a JIRA? There's an issue > with the BOM we use. > > I'll take care of this. > > Le 19/06/2015 10:16, Peter Palaga a écrit : > > hawkular-parent 16 with an upgrade to WF9 was just released and I have > > sent PRs to all projects on my list. -- P > > > > On 17/06/15 09:08, Thomas Heute wrote: > >> > >> We have to upgrade to WF9 to get more data out of WF9. > >> > >> there are quite some changes to be made: > >> - Parent declares the version of WF to use and BOM: > >> here is my branch: > >> https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 > >> - Accounts need to upgrade to KC 1.3 (to be released this week) > >> Juca will work on this > >> - Bus/Nest needs to adapt > >> here is my branch > >> https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs > another > >> patch from Mazz) > >> - Agent also needs some changes. > >> > >> WF 9 GA is supposed to go out at any point now, let's try to > coordinate > >> around that, if you have a release pending, think of that. > >> > >> BTW, I tried to reflect the dependencies between component, would have > >> been easier if everyone could respect our standards, in particular: > >> - declare all dependencies at the root pom > >> - use <version./groupid/> in pom properties. > >> So please fix this if you do not follow those basic rules. > >> > >> PS: for the upstream project, it is ok if all dependencies don't fully > >> align, for instance 2 components could depend on 2 different > versions of > >> the parent. > >> > >> Thomas > >> > >> > >> _______________________________________________ > >> 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 >

Ah, I assumed that jira was just for updating the Docker image to WF9 :) On 19/06/15 11:05 AM, Thomas Segismont wrote: > You've assigned it to Matt. Is that intentional? > > Le 19/06/2015 16:18, Thomas Heute a écrit : >> https://issues.jboss.org/browse/HWKMETRICS-145 >> >> On 06/19/2015 01:22 PM, Thomas Segismont wrote: >>> Can you close your PR against Metrics and open a JIRA? There's an issue >>> with the BOM we use. >>> >>> I'll take care of this. >>> >>> Le 19/06/2015 10:16, Peter Palaga a écrit : >>>> hawkular-parent 16 with an upgrade to WF9 was just released and I have >>>> sent PRs to all projects on my list. -- P >>>> >>>> On 17/06/15 09:08, Thomas Heute wrote: >>>>> We have to upgrade to WF9 to get more data out of WF9. >>>>> >>>>> there are quite some changes to be made: >>>>> - Parent declares the version of WF to use and BOM: >>>>> here is my branch: >>>>> https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 >>>>> - Accounts need to upgrade to KC 1.3 (to be released this week) >>>>> Juca will work on this >>>>> - Bus/Nest needs to adapt >>>>> here is my branch >>>>> https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs >>> another >>>>> patch from Mazz) >>>>> - Agent also needs some changes. >>>>> >>>>> WF 9 GA is supposed to go out at any point now, let's try to >>> coordinate >>>>> around that, if you have a release pending, think of that. >>>>> >>>>> BTW, I tried to reflect the dependencies between component, would have >>>>> been easier if everyone could respect our standards, in particular: >>>>> - declare all dependencies at the root pom >>>>> - use <version./groupid/> in pom properties. >>>>> So please fix this if you do not follow those basic rules. >>>>> >>>>> PS: for the upstream project, it is ok if all dependencies don't fully >>>>> align, for instance 2 components could depend on 2 different >>> versions of >>>>> the parent. >>>>> >>>>> Thomas >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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

Ah, I assumed that jira was just for updating the Docker image to WF9 :) On 19/06/15 11:05 AM, Thomas Segismont wrote: > You've assigned it to Matt. Is that intentional? > > Le 19/06/2015 16:18, Thomas Heute a écrit : >> https://issues.jboss.org/browse/HWKMETRICS-145 >> >> On 06/19/2015 01:22 PM, Thomas Segismont wrote: >>> Can you close your PR against Metrics and open a JIRA? There's an issue >>> with the BOM we use. >>> >>> I'll take care of this. >>> >>> Le 19/06/2015 10:16, Peter Palaga a écrit : >>>> hawkular-parent 16 with an upgrade to WF9 was just released and I have >>>> sent PRs to all projects on my list. -- P >>>> >>>> On 17/06/15 09:08, Thomas Heute wrote: >>>>> We have to upgrade to WF9 to get more data out of WF9. >>>>> >>>>> there are quite some changes to be made: >>>>> - Parent declares the version of WF to use and BOM: >>>>> here is my branch: >>>>> https://github.com/theute/hawkular-parent-pom/commits/HAWKULAR-244 >>>>> - Accounts need to upgrade to KC 1.3 (to be released this week) >>>>> Juca will work on this >>>>> - Bus/Nest needs to adapt >>>>> here is my branch >>>>> https://github.com/theute/hawkular-bus/tree/HAWKULAR-232 (needs >>> another >>>>> patch from Mazz) >>>>> - Agent also needs some changes. >>>>> >>>>> WF 9 GA is supposed to go out at any point now, let's try to >>> coordinate >>>>> around that, if you have a release pending, think of that. >>>>> >>>>> BTW, I tried to reflect the dependencies between component, would >>>>> have >>>>> been easier if everyone could respect our standards, in particular: >>>>> - declare all dependencies at the root pom >>>>> - use <version./groupid/> in pom properties. >>>>> So please fix this if you do not follow those basic rules. >>>>> >>>>> PS: for the upstream project, it is ok if all dependencies don't >>>>> fully >>>>> align, for instance 2 components could depend on 2 different >>> versions of >>>>> the parent. >>>>> >>>>> Thomas >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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