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

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

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

   **[Dan 
Tran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dantran)** 
opened 
**[SCM-99](https://issues.apache.org/jira/browse/SCM-99?redirect=false)** and 
commented
   
   Current implementation uses  -cfgd  ${startDate} option to retreive 
changelog from startDate to latest change log.
   However, -cfgd is not intended to be used this way.  It acutally returns the 
reverse which are the changelogs from the current view creation date to the 
date assigned to -cfgd.
   
   Therefore, the only solution is to retreive all changelogs and filter by 
start and end dates.
   
   
   
   ---
   
   **Attachments:**
   - 
[SCM-99.patch](https://issues.apache.org/jira/secure/attachment/12718642/SCM-99.patch)
 (_4.20 kB_)
   




> changelog is emtpy when using startDate is assigned
> ---------------------------------------------------
>
>                 Key: SCM-99
>                 URL: https://issues.apache.org/jira/browse/SCM-99
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-starteam
>         Environment: starteam, xp
>            Reporter: Dan Tran
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             Fix For: 1.0-beta-2
>
>         Attachments: SCM-99.patch
>
>
> Current implementation uses  -cfgd  ${startDate} option to retreive changelog 
> from startDate to latest change log.
> However, -cfgd is not intended to be used this way.  It acutally returns the 
> reverse which are the changelogs from the current view creation date to the 
> date assigned to -cfgd.
> Therefore, the only solution is to retreive all changelogs and filter by 
> start and end dates.  



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

Reply via email to