2:37 a.m.
Hi *,
this was already discussed on several calls. Although I know of no
objections, I am putting it also here to give you all the last chance to
protest or discuss.
The plan is to move the Maven modules from Nest [1] and Bus [2] git
repositories to Commons repository [3].
Details:
* Nest and Bus Maven modules will be moved to Hawkular Commons git
repository
* Nest and Bus Maven modules will belong to groupId org.hawkular.commons
* All modules of the org.hawkular.commons incl. Nest and Bus will be
released together
* The new and old subcomponents of Commons (such as Nest, Bus,
Templates, c* driver, ...) will be allowed to depend on each other,
but clearly, they may not introduce circular dependencies.
* To help to keep control on which subcomponent depends on which other
subcomponents, the dependency management will happen on
the subcomponent level rather than in hawkular-commons-parent
* Components consuming Nest, Bus or any of the other subcomponents of
Hawkular Commons will have to declare just one version property
version.org.hawkular.commons to manage all the the artifacts they
need from commons
* As noted by Stefan, only such subcomponents should be allowed to be
hosted in Commons that are generic enough -i.e. that do not contain
any deep and specific domain knowledge. Move of Bus and Nest to
commons satisfies this.
Pros:
* Decrease the maintenance overhead by decreasing the number of git
repositories and by decreasing the number of Hawkular components
having independent release cycles - e.g. after a new release of
Hawkular Parent there is two component less to upgrade, two componets
less to release and n components less to upgrade that depend on Bus
and Nest
Cons:
* Loose some amount of design cleanness - Hawkular Commons hosts Maven
modules with clean logical borders that could be hosted and released
independently.
* Esp. the independent release cycle could be seen as an
advantage when fixing bugs and CVEs
Pseudo-con:
* Note that the new home of Nest and Bus does not prescribe any
component that consumed Commons so far to consume also Nest and Bus
from now on. Dependent components can still choose the artifacts to
depend on with an unchanged granularity: Who dependeded on embedded
c* so far can stay with it without depending on Bus or Nest.
I am going to work on this change now.
[1] https://github.com/hawkular/hawkular-nest
[2] https://github.com/hawkular/hawkular-bus
[3] https://github.com/hawkular/hawkular-commons
Thanks,
Peter
10:27 a.m.
FYI, Nest and Bus now live in commons [1] and Hawkular main is consuming
them from there [2], partly via Hawkular Accounts feature pack.
Note that the old Bus [3] and Nest [4] git repos are obsolete now.
Note that Nest sources were originaly hosted in Bus git repo [3] then
for some time in Hawkular main [5] repo and then for some time in a
separate git repo [4].
As the history of [4] is just two commits and there was no release from
there, I propose to delete [4].
[1]
https://github.com/hawkular/hawkular-commons/tree/master/hawkular-nest
https://github.com/hawkular/hawkular-commons/tree/2acedc8832053cc0bcc145c...
[2]
https://github.com/hawkular/hawkular/commit/7076a712655032f5cc749a94ed01e...
[3] https://github.com/hawkular/hawkular-bus
[4] https://github.com/hawkular/hawkular-nest
Thanks,
Peter
On 2015-12-04 11:20, Peter Palaga wrote:
3373
days inactive
3404
days old
2 comments
1 participants
participants (1)
-
Peter Palaga