[
http://jira.codehaus.org/browse/MCHANGELOG-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101857
]
Dennis Lundberg commented on MCHANGELOG-65:
-------------------------------------------
Hi Paul,
I can understand your frustration. Debugging SCM related events is not easy.
I'm not convinced that providing working SCM setups is the right way to go
though. Rather I would like to create a page devoted to understanding what
might go wrong and how to find out that actually went wrong.
Topics for that page could be:
- My changelog report is blank, but it shouldn't be
- How do I know if there's a bug in the changelog plugin or if something is
wrong with my SCM configuration
- How can I debug the SCM command
> 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: Wish
> Reporter: Paul Sundling
>
> 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
