[
https://issues.apache.org/jira/browse/MNG-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413618#comment-17413618
]
Michael Osipov edited comment on MNG-7221 at 9/12/21, 9:08 AM:
---------------------------------------------------------------
What about making a YT video and/or writing a blog post for your colleague or
for all people which explains the concept... or maybe even better create a pull
request to the documentation which improves it and explains the concept in a
better way...or maybe everything..
Apart from that If devs have to handle things they need to learn (understand)
tools independent of being a programming language/IDE or tools to use them
efficient.. what [~michael-o] has already condensed it to the important point.
Furthermore related to your response to the {{FUTURE}} vs. {{SNAPSHOT}} sounds
like you don't understand how many tools/IDE's and more important users would
be affected (millions of users; 14+ million users just in June 2021) and in the
end it would be breaking change which means it cannot be implemented for a 3.X
version...
I agree with [~michael-o] to close this issue.
was (Author: khmarbaise):
What about making a YT video and/or writing a blog post for your colleague or
for all people which explains the concept... or maybe even better create a pull
request to the documentation which improves it and explains the concept in a
better way...or maybe everything..
Apart from that If devs have to handle things they need to learn (understand)
tools independent of being a programming language/IDE or tools to use them
efficient.. what [~michael-o] has already condensed it to the important point.
Furthermore related to your response to the {{FUTURE}} vs. {{SNAPSHOT}} sounds
like you don't understand how many tools/IDE's and more important users would
be affected (millions of users; 14+ million users just in June 2021) and in the
end it would be breaking change which means it can not be implemented for a 3.X
version...
I agree with [~michael-o] to close this issue.
> Allow "FUTURE" as an alias for "SNAPSHOT"
> -----------------------------------------
>
> Key: MNG-7221
> URL: https://issues.apache.org/jira/browse/MNG-7221
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.8.2
> Reporter: Enrique Arizón Benito
> Priority: Minor
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> +underlined text+SNAPSHOT versioning is an excellent idea that solve many
> problems, still many people do not understand them, mostly because they do
> not have the time to read the related documentation or just get confused by
> blogs with incorrect information.
> After working with many developers with different skills and experience I
> have found that replacing SNAPSHOT by FUTURE offers a much more intuitive
> idea on how to use the maven snapshots.
> IMHO, allowing for nomenclature like "v1-FUTURE" as an alias for
> "v1-SNAPSHOT" will boost the perceived usability of maven to many non-expert
> developers.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
