[ http://jira.codehaus.org/browse/MCHANGES-50?page=comments#action_70771 ] Mike Perham commented on MCHANGES-50: -------------------------------------
I think the plugin is unable to determine the project ID automatically because it gets a "Please log in" response to its request for the project home page and so the IssueNavigator GET fails due to a null pid parameter. Make more sense? [INFO] Generate "Jira Report" report. log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.HttpClient). log4j:WARN Please initialize the log4j system properly. [INFO] JIRA lives at: http://jira.webifysolutions.com [INFO] JIRA URL http://jira.webifysolutions.com/browse/WR doesn't include a pid, trying to get it [INFO] Successfully reached JIRA. [ERROR] Unable to get JIRA pid using the url http://jira.webifysolutions.com/browse/WR [INFO] Downloading http://jira.webifysolutions.com/secure/IssueNavigator.jspa?view=rss&pid=null&sort er/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&de corator=none [WARNING] Received: [500] org.xml.sax.SAXParseException: Expected "</link>" to terminate element starting on line 9. at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3376) at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3370) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1697) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at javax.xml.parsers.SAXParser.parse(SAXParser.java:281) at org.apache.maven.plugin.jira.JiraXML.<init>(JiraXML.java:56) at org.apache.maven.plugin.jira.JiraReportGenerator.<init>(JiraReportGenerator.java:40) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:188) > Handle JIRA authentication failure > ---------------------------------- > > Key: MCHANGES-50 > URL: http://jira.codehaus.org/browse/MCHANGES-50 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-2 > Reporter: Mike Perham > Assigned To: Dennis Lundberg > Fix For: 2.0-beta-2 > > Attachments: MCHANGES-50.tar.gz > > > Private instances of JIRA require authentication. If the changes report > queries this server, the server returns a HTML 500 error page, rather than > the expected XML content and the changes plugin throws an exception. This > case should be handled and a warning printed to the screen (maybe with a hint > as to the parameter(s) they need to set) so the site generation can continue. > See http://jira.webifysolutions.com for instance. You can use this URL for > one-off testing of this fix. -- 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
