[jira] [Commented] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on MCHANGES-361:
---------------------------------

SUCCESS: Integrated in maven-plugins #6852 (See [https://builds.apache.org/job/maven-plugins/6852/])
MCHANGES-371: github-report shows body of issue as summary.

This was introduced with MCHANGES-361. (mfriedenhagen: [http://svn.apache.org/viewvc/?view=rev&rev=1751555])
* maven-changes-plugin/src/main/java/org/apache/maven/plugin/github/GitHubDownloader.java
* maven-changes-plugin/src/test/java/org/apache/maven/plugin/github/GitHubDownloaderTestCase.java


> GitHub issue ids don't appear in announcement.vm
> ------------------------------------------------
>
>                 Key: MCHANGES-361
>                 URL: https://issues.apache.org/jira/browse/MCHANGES-361
>             Project: Maven Changes Plugin
>          Issue Type: Bug
>          Components: github
>    Affects Versions: 2.11
>            Reporter: David Pilato
>            Assignee: Olivier Lamy (*$^¨%`£)
>            Priority: Minor
>             Fix For: 2.12
>
>
> When you generate a github announcement velocity file with default configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2 upgrade 
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0 
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2 upgrade  Issue: 74. 
> Changes:
> o Update to beyonder 2.0.0  Issue: 76. 
> o Update to elasticsearch 2.0.0  Issue: 73. 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)