[Hawkular-dev] WF 9 upgrade

[Thomas Heute]

It is definitely a low priority, not sure if it should be closed.
If this is important for us, we should make comments and push it to pass the prototype phase, if it doesn't help, we should move on.

But again, definitely not a high priority, even though it looks good on paper

Thomas



On 06/17/2015 04:04 PM, John Mazzitelli wrote:
> 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 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
>