[ODLPARENT-265] Do not declare depends-maven-plugin in odlparent Created: 29/Sep/21  Updated: 30/May/23

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

Type: Task Priority: High
Reporter: Robert Varga Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to ODLPARENT-264 Fix thread safety around depends-mave... Confirmed
Epic Link: Faster Builds

 Description   

This declaration is only used in SFT as far as I can tell. The plugin is quite dead upstream to the point of not having been updated for parallel builds (ODLPARENT-264).

Remove its declaration from odlparent/pom.xml, so downstreams are not tempted to use it.

There are a few downstream users:

 

ovsdb/southbound/southbound-it/pom.xml
ovsdb/hwvtepsouthbound/hwvtepsouthbound-it/pom.xml
controller/opendaylight/md-sal/mdsal-it-parent/pom.xml
infrautils/itestutils/parent/pom.xml
infrautils/caches/sample/it/pom.xml

all of which seems to point towards the need for better pax-exam integration.

 



 Comments   
Comment by Robert Varga [ 29/Sep/21 ]

If we solve ODLPARENT-262 correctly, then all the IT users should be easy to convert:

  • create a test @Component(immediate=true)
  • put test logic into the @Activate method, returning from it only all tests have passed (or throw a failure)
  • package the component into a feature
  • run SFT on the feature

This way SFT deals with all the container setup and execution, without the test needing to know anything about execution environment – which is way better than anything Pax-Exam-based can provide.

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