maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
Date Mon, 26 Oct 2015 01:27:27 GMT

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

ASF GitHub Bot commented on MCHANGES-361:
-----------------------------------------

Github user dadoonet closed the pull request at:

    https://github.com/apache/maven-plugins/pull/66


> 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)

Mime
View raw message