[ 
https://issues.apache.org/jira/browse/SCM-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961147#comment-17961147
 ] 

ASF GitHub Bot commented on SCM-362:
------------------------------------

jira-importer opened a new issue, #575:
URL: https://github.com/apache/maven-scm/issues/575

   **[Andrew 
Williams](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=handyande)**
 opened 
**[SCM-362](https://issues.apache.org/jira/browse/SCM-362?redirect=false)** and 
commented
   
   The AbstractManager has no support for calling update using the date 
parameter that the api advertises.
   This is ignored and a simple update with no date / version parameters is 
called instead.
   The providers have no way of accessing the Date parameter as it is dropped 
before they are called
   
   
   ---
   
   **Affects:** 1.0
   




> update command ignores date parameter
> -------------------------------------
>
>                 Key: SCM-362
>                 URL: https://issues.apache.org/jira/browse/SCM-362
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-api
>    Affects Versions: 1.0
>            Reporter: Andrew Williams
>            Priority: Blocker
>
> The AbstractManager has no support for calling update using the date 
> parameter that the api advertises.
> This is ignored and a simple update with no date / version parameters is 
> called instead.
> The providers have no way of accessing the Date parameter as it is dropped 
> before they are called



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to