[ http://jira.codehaus.org/browse/MCHANGES-50?page=comments#action_70661 ] Mike Perham commented on MCHANGES-50: -------------------------------------
Exactly. We do not want to use the JIRA report but have not configured our reportSets to exclude the report. So we get an exception every time it runs. I would rather this just be a warning complaining about insufficient configuration. It would be nice if you could document a best practice to configure the jiraPassword without hard coding it (e.g. through properties and profiles?) in the POM. > 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 > > > 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
