[
https://issues.apache.org/jira/browse/MRESOLVER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734198#comment-17734198
]
ASF GitHub Bot commented on MRESOLVER-220:
------------------------------------------
cstamas opened a new pull request, #301:
URL: https://github.com/apache/maven-resolver/pull/301
Instead to silently "send result" (that is false) to caller, as this makes
totally strange outcome: "failed to lock within 30sec" but caller did not wait
anything. Moreover, the bug where upgrade is attempted slips in unnoticed.
---
https://issues.apache.org/jira/browse/MRESOLVER-220
> Modify signaling for unsupported operations
> -------------------------------------------
>
> Key: MRESOLVER-220
> URL: https://issues.apache.org/jira/browse/MRESOLVER-220
> Project: Maven Resolver
> Issue Type: Task
> Reporter: Tamas Cservenak
> Priority: Major
>
> Lock upgrading is not supported, it is the caller that must be aware of this.
> Currently the code for all implementations returns {{false}} in case of lock
> upgrade attempted, same way as locking failed. IMHO, we should change this to
> some exception maybe?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
