You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2012/08/30 15:20:10 UTC
[all] maven-changes-plugin failed to parse JIRA XML.
I've started to see this SAXParseException in [codec] trunk and other
commons components. Ideas?
[INFO] Generating "JIRA Report" report --- maven-changes-plugin:2.7.1
Aug 30, 2012 9:16:52 AM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[INFO] Downloading from JIRA at:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310464&statusIds=5
ype=2&type=3&type=4&type=5&type=6&sorter/field=fixVersions&sorter/order=DESC&sorter/field=issuetype&sorter/order=ASC&sorter
pMax=100&reset=true&decorator=none
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.xml.sax.SAXParseException: The entity name must immediately
follow the '&' in the entity reference.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
Source)
at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
... 30 more
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by sebb <se...@gmail.com>.
On 30 August 2012 16:04, Gary Gregory <ga...@gmail.com> wrote:
> On Thu, Aug 30, 2012 at 10:58 AM, sebb <se...@gmail.com> wrote:
>
>> On 30 August 2012 15:28, Gary Gregory <ga...@gmail.com> wrote:
>> > On Thu, Aug 30, 2012 at 9:37 AM, sebb <se...@gmail.com> wrote:
>> >
>> >> On 30 August 2012 14:20, Gary Gregory <ga...@gmail.com> wrote:
>> >> > I've started to see this SAXParseException in [codec] trunk and other
>> >> > commons components. Ideas?
>> >>
>> >> JIRA was upgraded recently, perhaps the plugin is not very resilient
>> >> to XML formatting changes.
>> >>
>> >> Does the problem still occur with components that have not been
>> >> updated to CP 26?
>> >>
>> >
>> > It does not happen on BCEL which is on CP 25.
>>
>> What happens if you change BCEL to use CP 26?
>>
>
> It works (I committed it).
What about codec on CP 25?
Try to establish whether it is CP, JIRA or component related.
> Gary
>
>
>>
>> > Gary
>> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >> For additional commands, e-mail: dev-help@commons.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
>> > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
>> > Blog: http://garygregory.wordpress.com
>> > Home: http://garygregory.com/
>> > Tweet! http://twitter.com/GaryGregory
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by Gary Gregory <ga...@gmail.com>.
On Thu, Aug 30, 2012 at 10:58 AM, sebb <se...@gmail.com> wrote:
> On 30 August 2012 15:28, Gary Gregory <ga...@gmail.com> wrote:
> > On Thu, Aug 30, 2012 at 9:37 AM, sebb <se...@gmail.com> wrote:
> >
> >> On 30 August 2012 14:20, Gary Gregory <ga...@gmail.com> wrote:
> >> > I've started to see this SAXParseException in [codec] trunk and other
> >> > commons components. Ideas?
> >>
> >> JIRA was upgraded recently, perhaps the plugin is not very resilient
> >> to XML formatting changes.
> >>
> >> Does the problem still occur with components that have not been
> >> updated to CP 26?
> >>
> >
> > It does not happen on BCEL which is on CP 25.
>
> What happens if you change BCEL to use CP 26?
>
It works (I committed it).
Gary
>
> > Gary
> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by sebb <se...@gmail.com>.
On 30 August 2012 15:28, Gary Gregory <ga...@gmail.com> wrote:
> On Thu, Aug 30, 2012 at 9:37 AM, sebb <se...@gmail.com> wrote:
>
>> On 30 August 2012 14:20, Gary Gregory <ga...@gmail.com> wrote:
>> > I've started to see this SAXParseException in [codec] trunk and other
>> > commons components. Ideas?
>>
>> JIRA was upgraded recently, perhaps the plugin is not very resilient
>> to XML formatting changes.
>>
>> Does the problem still occur with components that have not been
>> updated to CP 26?
>>
>
> It does not happen on BCEL which is on CP 25.
What happens if you change BCEL to use CP 26?
> Gary
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by Gary Gregory <ga...@gmail.com>.
On Thu, Aug 30, 2012 at 9:37 AM, sebb <se...@gmail.com> wrote:
> On 30 August 2012 14:20, Gary Gregory <ga...@gmail.com> wrote:
> > I've started to see this SAXParseException in [codec] trunk and other
> > commons components. Ideas?
>
> JIRA was upgraded recently, perhaps the plugin is not very resilient
> to XML formatting changes.
>
> Does the problem still occur with components that have not been
> updated to CP 26?
>
It does not happen on BCEL which is on CP 25.
Gary
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by sebb <se...@gmail.com>.
On 30 August 2012 14:20, Gary Gregory <ga...@gmail.com> wrote:
> I've started to see this SAXParseException in [codec] trunk and other
> commons components. Ideas?
JIRA was upgraded recently, perhaps the plugin is not very resilient
to XML formatting changes.
Does the problem still occur with components that have not been
updated to CP 26?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by Gary Gregory <ga...@gmail.com>.
On Sep 15, 2012, at 16:50, Dennis Lundberg <de...@apache.org> wrote:
> On 2012-08-30 23:18, Dennis Lundberg wrote:
>> Hi
>>
>> You've stumbled upon
>> http://jira.codehaus.org/browse/MCHANGES-285
>> due to the recent upgrade of the ASF JIRA instance.
>
> The 2.8 version of the Changes Plugin has now been released. Do you want
> me to add the necessary configuration to use it in commons-parent?
Good idea, go ahead.
Gary
>
>> On 2012-08-30 15:20, Gary Gregory wrote:
>>> I've started to see this SAXParseException in [codec] trunk and other
>>> commons components. Ideas?
>>>
>>> [INFO] Generating "JIRA Report" report --- maven-changes-plugin:2.7.1
>>> Aug 30, 2012 9:16:52 AM org.apache.commons.httpclient.HttpMethodBase
>>> getResponseBody
>>> WARNING: Going to buffer response body of large or unknown size. Using
>>> getResponseBodyAsStream instead is recommended.
>>> [INFO] Downloading from JIRA at:
>>> http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310464&statusIds=5
>>> ype=2&type=3&type=4&type=5&type=6&sorter/field=fixVersions&sorter/order=DESC&sorter/field=issuetype&sorter/order=ASC&sorter
>>> pMax=100&reset=true&decorator=none
>>> [WARNING]
>>> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>>> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
>>> at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
>>> at
>>> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755)
>>> at
>>> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
>>> at
>>> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
>>> at
>>> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
>>> at
>>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
>>> at
>>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
>>> at
>>> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
>>> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>> Caused by: org.xml.sax.SAXParseException: The entity name must immediately
>>> follow the '&' in the entity reference.
>>> at
>>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>>> Source)
>>> at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
>>> Source)
>>> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>>> Source)
>>> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>>> Source)
>>> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>>> Source)
>>> at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
>>> Source)
>>> at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
>>> Source)
>>> at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>>> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
>>> ... 30 more
>>>
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by Dennis Lundberg <de...@apache.org>.
On 2012-08-30 23:18, Dennis Lundberg wrote:
> Hi
>
> You've stumbled upon
> http://jira.codehaus.org/browse/MCHANGES-285
> due to the recent upgrade of the ASF JIRA instance.
The 2.8 version of the Changes Plugin has now been released. Do you want
me to add the necessary configuration to use it in commons-parent?
> On 2012-08-30 15:20, Gary Gregory wrote:
>> I've started to see this SAXParseException in [codec] trunk and other
>> commons components. Ideas?
>>
>> [INFO] Generating "JIRA Report" report --- maven-changes-plugin:2.7.1
>> Aug 30, 2012 9:16:52 AM org.apache.commons.httpclient.HttpMethodBase
>> getResponseBody
>> WARNING: Going to buffer response body of large or unknown size. Using
>> getResponseBodyAsStream instead is recommended.
>> [INFO] Downloading from JIRA at:
>> http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310464&statusIds=5
>> ype=2&type=3&type=4&type=5&type=6&sorter/field=fixVersions&sorter/order=DESC&sorter/field=issuetype&sorter/order=ASC&sorter
>> pMax=100&reset=true&decorator=none
>> [WARNING]
>> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
>> at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
>> at
>> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755)
>> at
>> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
>> at
>> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
>> at
>> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
>> at
>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
>> at
>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
>> at
>> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
>> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> Caused by: org.xml.sax.SAXParseException: The entity name must immediately
>> follow the '&' in the entity reference.
>> at
>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>> Source)
>> at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
>> Source)
>> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)
>> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)
>> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)
>> at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
>> Source)
>> at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>> Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>> Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>> Source)
>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
>> Source)
>> at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
>> ... 30 more
>>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] maven-changes-plugin failed to parse JIRA XML.
Posted by Dennis Lundberg <de...@apache.org>.
Hi
You've stumbled upon
http://jira.codehaus.org/browse/MCHANGES-285
due to the recent upgrade of the ASF JIRA instance.
On 2012-08-30 15:20, Gary Gregory wrote:
> I've started to see this SAXParseException in [codec] trunk and other
> commons components. Ideas?
>
> [INFO] Generating "JIRA Report" report --- maven-changes-plugin:2.7.1
> Aug 30, 2012 9:16:52 AM org.apache.commons.httpclient.HttpMethodBase
> getResponseBody
> WARNING: Going to buffer response body of large or unknown size. Using
> getResponseBodyAsStream instead is recommended.
> [INFO] Downloading from JIRA at:
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310464&statusIds=5
> ype=2&type=3&type=4&type=5&type=6&sorter/field=fixVersions&sorter/order=DESC&sorter/field=issuetype&sorter/order=ASC&sorter
> pMax=100&reset=true&decorator=none
> [WARNING]
> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> at
> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755)
> at
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.xml.sax.SAXParseException: The entity name must immediately
> follow the '&' in the entity reference.
> at
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> Source)
> at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
> Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> Source)
> at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
> Source)
> at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> Source)
> at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
> ... 30 more
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org