[Hawkular-dev] WF 9 upgrade

Thomas Segismont tsegismo at redhat.com
Fri Jun 19 11:30:11 EDT 2015


I knew the question was worth asking :)

I'll start with testing the code, and see if I can do something for the 
Docker images build files. Does that work?

Le 19/06/2015 17:12, Matt Wringe a écrit :
> 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 at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>>>
>>>>> _______________________________________________
>>>>> hawkular-dev mailing list
>>>>> hawkular-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>>
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>



More information about the hawkular-dev mailing list