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

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

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

   **[Torbjorn Eikli 
Smorgrav](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=smorgrav)**
 opened 
**[SCM-174](https://issues.apache.org/jira/browse/SCM-174?redirect=false)** and 
commented
   
   BazaarUtils:
   - refactored execute cmd, added more debugging onfo (bazaar version)
   
   ChangLogCmd:
   - Avoid null and empty filesets in the ChangeSets
   
   General:
   - More precise javadoc
   
   TODO: The changelog report is now generating empty reports (but is not 
failing as before). I plan to fix that in next my next patch (take 2).
   
   
   ---
   
   **Attachments:**
   - 
[SCM-174-maven-scm-provider-bazaar.patch](https://issues.apache.org/jira/secure/attachment/12718783/SCM-174-maven-scm-provider-bazaar.patch)
 (_9.85 kB_)
   




> Bugfix changelog cmd (take 1) and some general refinements
> ----------------------------------------------------------
>
>                 Key: SCM-174
>                 URL: https://issues.apache.org/jira/browse/SCM-174
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-bazaar
>         Environment: Tested: Tck tests on WinXP and Linux (Gentoo) with 
> Bazaar 0.7 and Continuum with changelog report.
>            Reporter: Torbjorn Eikli Smorgrav
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             Fix For: 1.0-beta-3
>
>         Attachments: SCM-174-maven-scm-provider-bazaar.patch
>
>
> BazaarUtils:
>  - refactored execute cmd, added more debugging onfo (bazaar version) 
> ChangLogCmd:
>  - Avoid null and empty filesets in the ChangeSets
> General:
> - More precise javadoc 
> TODO: The changelog report is now generating empty reports (but is not 
> failing as before). I plan to fix that in next my next patch (take 2).



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

Reply via email to