[MPLUGIN-510] update plugin system requirements history structure

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.11.0
• Fix Version/s: 3.12.0
• Component/s: Plugin Reporting Plugin
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 22/Feb/24 07:31
• Updated: 24/Mar/24 07:13
• Resolved: 24/Mar/24 07:13

Description

in MPLUGIN-400, we added the feature with a list of versions of the plugin, associated to Maven and JDK prerequisite https://maven.apache.org/plugin-tools-archives/plugin-tools-3.7.0/maven-plugin-report-plugin/report-mojo.html#requirementshistories

=> started to use for example: https://maven.apache.org/plugins-archives/maven-assembly-plugin-3.6.0/plugin-info.html

this lead to questions: should we fill each and every past version? Or should we group by common prerequisites, showing only ranges?

Tested the range approach: https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/plugin-info.html

the range approach looks good: minimum lines (vs listing every version), clear choice for users (choose the latest in the range, or pick any intermediate one)

now, we need to rework the m-p-p configuration to replace "version" with "from" + "to", instead of hijacking the "version" field to store a String "from x to y"

Issue Links

• supercedes: MPLUGIN-400 add plugin system requirements history section
• links to: GitHub Pull Request #274