[
https://issues.apache.org/jira/browse/MINVOKER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958447#comment-17958447
]
Olivier Lamy commented on MINVOKER-289:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#533|https://github.com/apache/maven-invoker-plugin/issues/533].
> Support for shared invoker's Update-Snapshots Flag
> --------------------------------------------------
>
> Key: MINVOKER-289
> URL: https://issues.apache.org/jira/browse/MINVOKER-289
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 3.2.2
> Reporter: Tuomas Kiviaho
> Assignee: Slawomir Jaranowski
> Priority: Minor
> Labels: up-for-grabs
> Fix For: 3.4.0
>
>
> 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.10#820010)
