[
https://issues.apache.org/jira/browse/MPLUGIN-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-510:
----------------------------------
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"
was:
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"
> update plugin system requirements history structure
> ---------------------------------------------------
>
> Key: MPLUGIN-510
> URL: https://issues.apache.org/jira/browse/MPLUGIN-510
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
> Affects Versions: 3.11.0
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: 3.12.0
>
>
> 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"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
