[ 
https://jira.codehaus.org/browse/MPCHANGELOG-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MPCHANGELOG-67.
-------------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Visual Source Safe factory improvements
> ---------------------------------------
>
>                 Key: MPCHANGELOG-67
>                 URL: https://jira.codehaus.org/browse/MPCHANGELOG-67
>             Project: Maven 1.x Changelog Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.8.1
>         Environment: maven-changelog-plugin v.1.7.3
> VSS v. 6.0
> Windows XP pro
>            Reporter: Freddy Mallet
>         Attachments: maven-changelog-vssimpl.zip
>
>
> The issue 'MPCHANGELOG-65' raises a real problem since vss feed is formatted 
> according to regional settings of the machine. Moreover there is no way in 
> java to get those regional settings (cf: 
> http://forum.java.sun.com/thread.jspa?threadID=24929&messageID=2636438). So, 
> by default we can expect to get the following VSS date format : 'MM/dd/yy 
> h:mma'  which could be overwritten if necessary with property 
> 'maven.changelog.vsslib.dateFormat'. 
> For instance, in Geneva  (fr_CH), the correct date format is 'dd/MM/yy HH:mm'.
> The patch enclosed include this improvement with others minor changes:
>  
> - Add jUnit tests with dummy VSS history feed
> - Fix bug when vss project specified in the scm connection string ended with 
> '/'. In that case we got an exception 'String out of range : -1'
> - Patch submitted with issue 'MPCHANGELOG-65' to fix bug when vss history 
> feed contained label items didn't pass junit tests. 
> thanks



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to