Bug 6278: Copy karaf-parent from controller to odlparent
As discussed in the MD-SAL call, there is an architectural need to move
karaf-parent from the controller project to the odlparent project. This
is particularly useful for karaf upgrades, since right now a bump in karaf
version within odlparent requires a rebuild of controller to reflect the
change in karaf-parent, and our build jobs are not set up to support such
a process.
The move process will be handled in multiple steps:
1) Copy karaf-parent, karaf-branding and opendaylight-karaf-resources to
odlparent. All three of these should belong in odlparent. All three must
be moved since karaf-parent depends on the latter two artifacts. Since
controller depends on odlparent (and not the other way around), they must
be moved upstream to odlparent.
2) Have controller's karaf-parent derive from odlparent's karaf-parent.
This preserves the ability for downstream consumers to derive from the
controller karaf-parent in the interim, while allowing changes to odlparent's
karaf-parent to be recognized since controller does not need to be rebuilt.
[THIS PATCH]
This also involves removing karaf-branding and opendaylight-karaf-resources
from the controller project, since they are no longer needed. There are two
consumers that need to be patched:
lispflowmapping: https://git.opendaylight.org/gerrit/42647
vtn: https://git.opendaylight.org/gerrit/42648
3) Change all downstream projects to utilize odlparent's karaf-parent. This
is future work and will be done in several patches.
4) Remove controller's karaf-parent once we feel all downstream consumers
are using the odlparent's karaf-parent.
Change-Id: Ib42ff5212bbfb93883346a19855544df4fb06d61
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>
24 files changed: