You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/05/21 17:25:00 UTC
[jira] [Updated] (MINVOKER-289) Support for shared invoker's Update-Snapshots Flag
[ https://issues.apache.org/jira/browse/MINVOKER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Slawomir Jaranowski updated MINVOKER-289:
-----------------------------------------
Fix Version/s: (was: 3.3.0)
> Support for shared invoker's Update-Snapshots Flag
> --------------------------------------------------
>
> Key: MINVOKER-289
> URL: https://issues.apache.org/jira/browse/MINVOKER-289
> Project: Maven Invoker Plugin
> Issue Type: New Feature
> Affects Versions: 3.2.2
> Reporter: Tuomas Kiviaho
> Priority: Major
> Labels: up-for-grabs
>
> The dependencies might contain such snapshots that are not up-to-date in local repo. My first invoker goal is \{{versions:resolve-ranges}} with \{{allowSnapshots}} enabled (depending on external properties) and my invoker project pom will be resolved with some SNAPSHOT previously unknown to the local repository.
> There won't be any attempt to load these unless there is a way to set \{{setUpdateSnapshots}} request param to true.
> Would it be possible to add this as configuration parameter.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)