You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2007/07/17 23:08:13 UTC
[jira] Closed: (MCHANGELOG-65) documentation samples for working
changelog reports for each supported SCM
[ http://jira.codehaus.org/browse/MCHANGELOG-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGELOG-65.
-------------------------------------
Resolution: Fixed
I've added a final piece of information to the FAQ. This is all the advice I can think of.
I've staged the site at the same location, if you want to have a look at it.
Closing issue this now.
> documentation samples for working changelog reports for each supported SCM
> --------------------------------------------------------------------------
>
> Key: MCHANGELOG-65
> URL: http://jira.codehaus.org/browse/MCHANGELOG-65
> Project: Maven 2.x Changelog Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Paul Sundling
> Assignee: Dennis Lundberg
> Fix For: 2.1
>
>
> I've spent quite a while trying to get a changelog report that wasn't blank using perforce.
> It would be nice to have a sample pom.xml listed for each of the supported SCMs. That way I could know for sure it wasn't my setup and whether I'm experiencing a bug or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira