[
https://issues.apache.org/jira/browse/MWRAPPER-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847367#comment-17847367
]
Nils Breunese edited comment on MWRAPPER-135 at 5/17/24 4:53 PM:
-----------------------------------------------------------------
Also, if {{wrapper:wrapper}} is run on a project that already contains this
property in {{maven-wrapper.properties}} (for instance when updating Maven
Wrapper), would it make sense to use this type by default when {{type}} is not
explicitly set via {{{}-Dtype={}}}? If so, I guess this can also be implemented
via a separate ticket.
was (Author: breun):
Also, if {{wrapper:wrapper}} is run on a project that already contains this
property in {{maven-wrapper.properties}} (to update Maven Wrapper), would it
make sense to use this type by default when {{type}} is not explicitly set via
{{{}-Dtype={}}}? If so, I guess this can also be implemented via a separate
ticket.
> Provide a reliable way to determine the Maven Wrapper type
> ----------------------------------------------------------
>
> Key: MWRAPPER-135
> URL: https://issues.apache.org/jira/browse/MWRAPPER-135
> Project: Maven Wrapper
> Issue Type: Task
> Components: Maven Wrapper Plugin
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 3.3.2
>
>
> Just like MWRAPPER-134 but for type. I completely forgot about this. As this
> way, tooling can figure out not only version but type (also for humans, just
> peek at properties).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
