[ODLPARENT-41] karaf-parent belongs in odlparent Created: 27/Jul/16  Updated: 24/Jan/18  Resolved: 12/Sep/17

Status: Resolved
Project: odlparent
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Ryan Goulding Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6278

 Comments   
Comment by Robert Varga [ 01/Aug/16 ]

https://git.opendaylight.org/gerrit/#/q/topic:move-karaf-parent

Comment by Vratko Polak [ 05/Aug/16 ]

Will opendaylight-karaf-empty be moved as well?
It is just a trivial application of karaf-parent used for SingleFeatureTest (which is in Odlparent), so for purposes of Karaf version bumping it would be better placed in Odlparent (rather than Controller).
Ideally, only opendaylight-karaf should be left in Controller, as that is its

{project}

-karaf.

Comment by Stephen Kitt [ 05/Aug/16 ]

(In reply to Vratko Polák from comment #2)
> Will opendaylight-karaf-empty be moved as well?
> It is just a trivial application of karaf-parent used for SingleFeatureTest
> (which is in Odlparent), so for purposes of Karaf version bumping it would
> be better placed in Odlparent (rather than Controller).
> Ideally, only opendaylight-karaf should be left in Controller, as that is
> its

{project}

-karaf.

Indeed, we probably should move it.

Comment by Stephen Kitt [ 05/Aug/16 ]

(In reply to Stephen Kitt from comment #3)
> (In reply to Vratko Polák from comment #2)
> > Will opendaylight-karaf-empty be moved as well?
> > It is just a trivial application of karaf-parent used for SingleFeatureTest
> > (which is in Odlparent), so for purposes of Karaf version bumping it would
> > be better placed in Odlparent (rather than Controller).
> > Ideally, only opendaylight-karaf should be left in Controller, as that is
> > its

{project}

-karaf.
>
> Indeed, we probably should move it.

Actually I'm not sure it's relevant anymore...

Comment by Robert Varga [ 05/Aug/16 ]

Quite a few projects still reference it in their features/pom.xml, as they have not been converted to features-parent: sxp, didm, ttp, lacp, topoprocessing, ...

It is also used for config-it-base and mdsal-it-base.

Comment by Ryan Goulding [ 05/Aug/16 ]

Sure, I'll move it.

Generated at Wed Feb 07 20:27:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.