[MDSAL-210] Beryllium: circular dependency on Controller Created: 29/Nov/16  Updated: 09/Mar/18  Resolved: 05/Jan/17

Status: Resolved
Project: mdsal
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Won't Do 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: 7261

 Description   

Autorelease jobs now require cycle-free pom dependecies. Mdsal is now breaking Beryllium autorelease.
Beryllium is not actively maintained anymore, but autorelease should be ready in case a security fix is needed.

The offending POM modules are:

  • dom/sal-test-model/pom.xml: Parent set as sal-parent, should be easy to migrate to a mdsal-located parent.
  • dom/mdsal-artifacts/pom.xml: Contains many controller artifacts, should be trimmed-down to mdsal artifacts only. Also, groupId should not be controller (this may require changes to other projects).

 Comments   
Comment by Vratko Polak [ 04/Jan/17 ]

I got it wrong. Beryllium autorelease itself works, it is just autorelease-project-report-beryllium which has been failing.
Also, autorelease commented-out [0] Beryllium dependency sorting, so this Bug is not detected anymore.

Lowering priority.

[0] https://git.opendaylight.org/gerrit/49671

Comment by Vratko Polak [ 05/Jan/17 ]

> autorelease-project-report-beryllium which has been failing

Releng people have given up and disabled merge order computations for Beryllium.
So nothing is failing now, but having a cycle is still unpleasant.

Comment by Martin Ciglan [ 05/Jan/17 ]

As Beryllium is not supported anymore, closing this issue. Discussed with Vratko too.

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