[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310370#comment-310370 ] Gary Clayburg commented on MCHANGES-285: Dennis, I created MCHANGES-291 to address this issue. Thanks. > SAXException parsing JIRA XML from JIRA 5.1 > > > Key: MCHANGES-285 > URL: https://jira.codehaus.org/browse/MCHANGES-285 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.7.1 > Environment: osx rhel sun java 1.6.0_30 >Reporter: Micah Whitacre >Assignee: Dennis Lundberg > Fix For: 2.8 > > Attachments: patch-2.7.x.txt, patch.txt > > > When trying to generate a changes report from a JIRA instance running 5.1[1] > I get the following exception > [INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1 > Jul 16, 2012 5:32:53 PM 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://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rss&pid=10670&component=kepler-client&component=kepler-parent&status=Verified&status=Closed&resolution=1&resolution=12&tempMax=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:317) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) > 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) >
[jira] (MCHANGES-291) Cannot authenticate to Jira OnDemand
Gary Clayburg created MCHANGES-291:
--
Summary: Cannot authenticate to Jira OnDemand
Key: MCHANGES-291
URL: https://jira.codehaus.org/browse/MCHANGES-291
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.8
Reporter: Gary Clayburg
This plugin recently stopped working for our project that uses Atlassian Jira
OnDemand.
It now appears to fail with this 400 error. I'm thinking this is due to recent
changes in the way that Jira OnDemand is doing authentication. I get a similar
error in a browser if the session is not authenticated. Does anyone else use
Jira OnDemand with this plugin?
{code}
$ mvn -f pom_changestest.xml changes:jira-report
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ changes-tests
---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
[INFO] Downloading from JIRA at:
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100&reset=true&jqlQuery=project+%3D+OIAM+AND+fixVersion+in+%28%221.0.5%22%29+AND+status+in+%28Closed%29+AND+resolution+in+%28Fixed%29+ORDER+BY+priority+DESC%2C+created+DESC
[WARNING] Downloading from JIRA failed. Received: [400]
[WARNING] JIRA file C:\QA\integration-tests\target\jira-results.xml doesn't
exist.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 3.340s
[INFO] Finished at: Fri Oct 05 09:32:48 MDT 2012
[INFO] Final Memory: 18M/152M
[INFO]
{code}
The pom.xml file is this:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.urlremoved
changes-tests
jar
changes-tests
1.22
JIRA
https://urlremoved.jira.com/browse/OIAM
changes-tests
org.apache.maven.plugins
maven-changes-plugin
2.8
true
1.0.5
justsomed...@somewhere.com
EnterRealPasswordHere
{code}
I also notice that even this test is executed in debug mode, it indicates that
login to Jira succeeded even when an invalid password is supplied:
{code}
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
[DEBUG] Encoding JQL query project = OIAM AND fixVersion in ("1.0.5") AND
status in (Closed) AND resolution in (Fixed) ORDER BY priority DESC, created
DESC
[DEBUG] Encoded JQL query
project+%3D+OIAM+AND+fixVersion+in+%28%221.0.5%22%29+AND+status+in+%28Closed%29+AND+resolution+in+%28Fixed%29+ORDER+BY+priority+DESC%2C+created+DESC
[DEBUG] JIRA lives at: https://urlremoved.jira.com
[DEBUG] Login URL:
https://urlremoved.jira.com/login.jsp?os_destination=/secure/&os_username=justsomedude%40somewhere.com&os_password=*
[DEBUG] Successfully logged in into JIRA.
[DEBUG] download jira issues from url
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100&reset=true&jqlQuery=project+%3D+OIAM+AND+fixVersion+in+%28%221.0.5%22%29+AND+status+in+%28Closed%29+AND+resolution+in+%28Fixed%29+ORDER+BY+priority+DESC%2C+created+DESC
[INFO] Downloading from JIRA at:
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100&reset=true&jqlQuery=project+%3D+OIAM+AND+fixVersion+in+%28%221.0.5%22%29+AND+status+in+%28Closed%29+AND+resolution+in+%28Fixed%29+ORDER+BY+priority+DESC%2C+created+DESC
[WARNING] Downloading from JIRA failed. Received: [400]
{code}
This issue is related to MCHANGES-285
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[
https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310305#comment-310305
]
Gary Clayburg commented on MCHANGES-285:
Hey guys, this issue was working for me using Jira OnDemand. It now appears to
fail with this 400 error. I'm thinking this is due to recent changes in the
way that Jira OnDemand is doing authentication. I get a similar error in a
browser if the session is not authenticated. Does anyone else use Jira
OnDemand with this plugin?
{code}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.8-SNAPSHOT:jira-report (default-cli) @
changes-tests ---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
[INFO] Downloading from JIRA at:
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100&reset=true&jqlQuery=project+%3D+OIAM+AND+fixVersion+in+%28%221.0.5%22%29+AND+status+in+%28Closed%29+AND+resolution+in+%28Fixed%29+ORDER+BY+priority+DESC%2C+created+DESC
[WARNING] Downloading from JIRA failed. Received: [400]
{code}
> SAXException parsing JIRA XML from JIRA 5.1
>
>
> Key: MCHANGES-285
> URL: https://jira.codehaus.org/browse/MCHANGES-285
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.7.1
> Environment: osx rhel sun java 1.6.0_30
>Reporter: Micah Whitacre
>Assignee: Dennis Lundberg
> Fix For: 2.8
>
> Attachments: patch-2.7.x.txt, patch.txt
>
>
> When trying to generate a changes report from a JIRA instance running 5.1[1]
> I get the following exception
> [INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1
> Jul 16, 2012 5:32:53 PM 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://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rss&pid=10670&component=kepler-client&component=kepler-parent&status=Verified&status=Closed&resolution=1&resolution=12&tempMax=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:317)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> 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.invo
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306500#comment-306500 ] Gary Clayburg commented on MCHANGES-285: I finally got back to looking at this issue. This patch worked great for me. Thanks for the help, guys. So what is the process for getting this patch committed and and released? > SAXException parsing JIRA XML from JIRA 5.1 > > > Key: MCHANGES-285 > URL: https://jira.codehaus.org/browse/MCHANGES-285 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.7.1 > Environment: osx rhel sun java 1.6.0_30 >Reporter: Micah Whitacre > Attachments: patch-2.7.x.txt, patch.txt > > > When trying to generate a changes report from a JIRA instance running 5.1[1] > I get the following exception > [INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1 > Jul 16, 2012 5:32:53 PM 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://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rss&pid=10670&component=kepler-client&component=kepler-parent&status=Verified&status=Closed&resolution=1&resolution=12&tempMax=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:317) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) > 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.X
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[
https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305669#comment-305669
]
Gary Clayburg commented on MCHANGES-285:
Ton,
Thank your for attaching this patch. I was able to install the patch and build
the plugin. However, I am getting this new error:
{code}
$ mvn -f pom-changestest.xml changes:jira-report
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.7.1:jira-report (default-cli) @ changes-tests
---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
Aug 6, 2012 6:29:48 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[ERROR] Unable to extract a JIRA pid from the page at the url
https://urlremoved.jira.com/browse/OIAM
[ERROR] Error accessing https://urlremoved.jira.com/browse/OIAM
java.lang.RuntimeException: The issue management URL in the POM does not
include a pid, and it was not possible to extract it from the page at that URL.
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:230)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:144)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:354)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:187)
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:319)
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)
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
{code}
This is the slimmed down pom file I am using:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.urlremoved
changes-tests
jar
changes-tests
1.22
JIRA
https://urlremoved.jira.com/browse/OIAM
changes-tests
org.apache.maven.plugins
maven-changes-plugin
2.7.1
true
1.0.5
gary.clayb...@urlremoved.com
password1234
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[
https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305669#comment-305669
]
Gary Clayburg edited comment on MCHANGES-285 at 8/6/12 7:40 PM:
Ton,
Thank your for attaching this patch. I was able to install the patch and build
the plugin. However, I am getting this new error:
{code}
$ mvn -f pom-changestest.xml changes:jira-report
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.7.1:jira-report (default-cli) @ changes-tests
---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
Aug 6, 2012 6:29:48 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[ERROR] Unable to extract a JIRA pid from the page at the url
https://urlremoved.jira.com/browse/OIAM
[ERROR] Error accessing https://urlremoved.jira.com/browse/OIAM
java.lang.RuntimeException: The issue management URL in the POM does not
include a pid, and it was not possible to extract it from the page at that URL.
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:230)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:144)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:354)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:187)
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:319)
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)
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
{code}
This is the slimmed down pom file I am using:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.urlremoved
changes-tests
jar
changes-tests
1.22
JIRA
https://urlremoved.jira.com/browse/OIAM
changes-tests
org.apache.maven.plugins
maven-changes-plugin
2.7.1
true
1.0.5
gary.clayb...@urlremoved.com
password1234
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305572#comment-305572 ] Gary Clayburg commented on MCHANGES-285: I seem to be having a very similar problem. Maybe this issue is related to our use of Jira on demand? > SAXException parsing JIRA XML from JIRA 5.1 > > > Key: MCHANGES-285 > URL: https://jira.codehaus.org/browse/MCHANGES-285 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.7.1 > Environment: osx rhel sun java 1.6.0_30 >Reporter: Micah Whitacre > > When trying to generate a changes report from a JIRA instance running 5.1[1] > I get the following exception > [INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1 > Jul 16, 2012 5:32:53 PM 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://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rss&pid=10670&component=kepler-client&component=kepler-parent&status=Verified&status=Closed&resolution=1&resolution=12&tempMax=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:317) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) > 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) >
