[
https://issues.apache.org/jira/browse/MWRAPPER-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nils Breunese updated MWRAPPER-134:
-----------------------------------
Description:
I use [Renovate|https://github.com/renovatebot/renovate] to automatically keep
dependencies up-to-date and I noticed that the upgrade to Maven Wrapper 3.3.0
removed the {{wrapperUrl}} line from
{{{}.mvn/wrapper/maven-wrapper.properties{}}}. I guess that is related to
MWRAPPER-120.
A couple of my colleagues implemented the support for keeping Maven Wrapper
up-to-date in Renovate, and I believe Renovate currently determines the version
of Maven Wrapper based on the {{wrapperUrl}} property, so I think that logic
may need to be updated after this change. Without the {{wrapperUrl}} property,
I think currently the only option to determine the Maven Wrapper version is
parsing the {{mvnw}} / \{{mvnw.cmd}} scripts themselves, but that sounds like a
clunky and unreliable way.
In a discussion on the maven-users mailinglist, the idea was posted to add a
dedicated property for this (e.g. {{{}wrapperVersion{}}}), which can be read by
external tools.
was:
I use [Renovate|https://github.com/renovatebot/renovate] to automatically keep
dependencies up-to-date and I noticed that the upgrade to Maven Wrapper 3.3.0
removed the {{wrapperUrl}} line from
{{{}.mvn/wrapper/maven-wrapper.properties{}}}. I guess that is related to
MWRAPPER-120.
A couple of my colleagues implemented the support for keeping Maven Wrapper
up-to-date in Renovate, and I believe Renovate currently determines the version
of Maven Wrapper based on the {{wrapperUrl}} property, so I think that logic
may need to be updated after this change. Without the {{wrapperUrl}} property,
I think currently the only option to determine the Maven Wrapper version is
parsing the `mvnw` / `./mvnw.bat` scripts themselves, but that sounds like a
clunky and unreliable way.
In a discussion on the maven-users mailinglist, the idea was posted to add a
dedicated property for this (e.g. {{{}wrapperVersion{}}}), which can be read by
external tools.
> Provide a reliable way to determine the Maven Wrapper version
> -------------------------------------------------------------
>
> Key: MWRAPPER-134
> URL: https://issues.apache.org/jira/browse/MWRAPPER-134
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Plugin
> Affects Versions: 3.3.0
> Reporter: Nils Breunese
> Assignee: Tamas Cservenak
> Priority: Normal
> Fix For: 3.3.1
>
>
> I use [Renovate|https://github.com/renovatebot/renovate] to automatically
> keep dependencies up-to-date and I noticed that the upgrade to Maven Wrapper
> 3.3.0 removed the {{wrapperUrl}} line from
> {{{}.mvn/wrapper/maven-wrapper.properties{}}}. I guess that is related to
> MWRAPPER-120.
> A couple of my colleagues implemented the support for keeping Maven Wrapper
> up-to-date in Renovate, and I believe Renovate currently determines the
> version of Maven Wrapper based on the {{wrapperUrl}} property, so I think
> that logic may need to be updated after this change. Without the
> {{wrapperUrl}} property, I think currently the only option to determine the
> Maven Wrapper version is parsing the {{mvnw}} / \{{mvnw.cmd}} scripts
> themselves, but that sounds like a clunky and unreliable way.
> In a discussion on the maven-users mailinglist, the idea was posted to add a
> dedicated property for this (e.g. {{{}wrapperVersion{}}}), which can be read
> by external tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
