[jira] Commented: (MCHANGES-75) Setting maxEntries results in incorrect JIRA results

["John Casey (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MCHANGES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92519 ] 

John Casey commented on MCHANGES-75:
------------------------------------

The same thing happens if I use the issueManagement URL: 

http://jira.codehaus.org/secure/BrowseProject.jspa?pid=10500

(I had been using http://jira.codehaus.org/browse/MNG)

> Setting maxEntries results in incorrect JIRA results
> ----------------------------------------------------
>
>                 Key: MCHANGES-75
>                 URL: http://jira.codehaus.org/browse/MCHANGES-75
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-2
>         Environment: maven 2.0.6
>            Reporter: John Casey
>
> When I configure maxEntries == 500 and point the jira-report at http://jira.codehaus.org/browse/MNG, it fails to parse the resulting XML, saying it has exceeded 64,000 entity expansions (something to do with SAX). The error is:
> org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
> When I wget the URL that the changes plugin has generated: 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10500&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=500&reset=true&decorator=none
> it shows results from XWIRE and XULUX...clearly not limited to MNG.

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