[
https://jira.codehaus.org/browse/MCHANGELOG-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328476#comment-328476
]
Jörg Sesterhenn commented on MCHANGELOG-107:
--------------------------------------------
You could do it by convention ([as maven always
does|http://books.sonatype.com/mvnref-book/reference/installation-sect-conventionConfiguration.html]).
My suggestion for defaultformat would be "artifactId-version".
If you feel you must, you could make it configurable (e.g. by regexp with
matching group for artifact version).
Alternatively you could provide a complete Changelog history grouped by tag
(MCHANGELOG-137) . That way naming would not matter and the request of not
having to manipulate the pluginconfiguration for every release would be
satisfied.
> generate changelog since previouse release
> ------------------------------------------
>
> Key: MCHANGELOG-107
> URL: https://jira.codehaus.org/browse/MCHANGELOG-107
> Project: Maven 2.x Changelog Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Grzegorz Kochanski
>
> Now mvn release:release generates changelog for last 2 days.
> The default behavior should be changelog since previous released version.
> To simulate behavior now you have to add to pom.xml:
> <plugin>
> <artifactId>maven-changelog-plugin</artifactId>
> <configuration>
> <type>tag</type>
> <tags>
> <tag implementation="java.lang.String">someApplication-1_6</tag>
> <tag implementation="java.lang.String">HEAD</tag>
> </tags>
> </configuration>
> </plugin>
> and change the someApplication-1_6 with someApplication-1_7 after successful
> release.
> And you have to repeat it for every release you perform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
