Overview

• Introduction
• Goals
• Usage
• FAQ
• Using the XML Schema

Reference

• changes.xml
• changes.xsd

Samples

• Sample Changes Report
• Live JIRA Report

Examples

• Alternate Location for the changes.xml File
• Check Your changes.xml File
• Configuring the Trac Report
• Customizing the JIRA Report
• Include an Announcement File in Your Packaging
• SMTP Authentication
• Specifying the Mail Sender
• Using a Custom Announcement Template
• Validate Your changes.xml File

Project Documentation

• Project Information
• Project Reports

Maven Projects

• Ant Tasks
• Archetype
• Doxia
• JXR
• Maven 1.x
• Maven 2
• Plugins
• SCM
• Shared Components
• Surefire
• Wagon

What's the difference between the changes-maven-plugin at Mojo and this one?

This plugin started out at the Mojo project. In March of 2006 the plugin was moved to Apache and the Maven sandbox. So it's the same plugin, but this one is newer.

[top]

---

I get a org.xml.sax.SAXParseException, when generating the JIRA Report. What can do about it?

If you have a lot of entities in the xml file returned from your JIRA installation, you might get an error like this one, when you run the JIRA Report:

org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
        

If that happens you need to tell the xml parser to use a higher limit. This can be accomplished by adding a command line parameter. In the following example we have set it to double the original value:

mvn -DentityExpansionLimit=128000 ...
        

Unfortunately we have not been able to set this in Java. If someone knows how to do this, then please reopen MCHANGES-75, and tell us how. It would be nicer if this could be set using a parameter in the POM.

[top]