[
https://issues.apache.org/jira/browse/MASSEMBLY-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813370#comment-17813370
]
ASF GitHub Bot commented on MASSEMBLY-1016:
-------------------------------------------
hboutemy commented on PR #181:
URL:
https://github.com/apache/maven-assembly-plugin/pull/181#issuecomment-1921890865
from experience filling that history, what is hard is that in general, there
is an issue that tracks a system prerequisite update, then it's easy to write
down the beginning of the range (since release x of the plugin, Java
prerequisite is 8): what is important is to know the last previous plugin
release that has the previous prerequisite (Java prerequisite 7 was ok until
release "prev(x)").
but clarifying that the plugin release is from x to y is a huge helper: we
could propose a configuration that defines either `version` or `from` + `to`
we'll need to copy/paste that comment to a MPLUGIN issue...
> clarify and fix plugin system requirements history
> --------------------------------------------------
>
> Key: MASSEMBLY-1016
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1016
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 3.6.0
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: 3.7.0
>
>
> as found in MASSEMBLY-990, there are issues in the data
> writing plugin versions in the form of "from x to y" clarifies
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
