[MNG-7667] IT suite fails if tested Maven lifecycle binding contains plugin version not in bootstrap - ASF JIRA

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: Integration Tests
Labels:
None

Description

A problem with our IT suite:

Version of Maven used in outer build (the one we invoke on CLI, usually a "stable/release" maven version) and the version of Maven used in inner build (the version being tested) usually differ, that's the point of test suite after all.

Problem: while outer build applies "best practices" re build, it locks down all the plugin versions, the inner build use "bare" or "simple" POMs, so it is totally dependent on the plugin versions found in default lifecycle bindings of the Maven version being tested.

The "bootstrap" list (list of artifacts we pre-populate into local repository before ITs start) is really not a static list, but is dynamic.

Or, in other words, today's bootstrap list should contain all the plugin versions of all the plugins bound in any Maven version out there.