[jira] Updated: (MCHANGES-50) Handle JIRA authentication failure
[ http://jira.codehaus.org/browse/MCHANGES-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-50: Component/s: jira-report > Handle JIRA authentication failure > -- > > Key: MCHANGES-50 > URL: http://jira.codehaus.org/browse/MCHANGES-50 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.0-beta-2 >Reporter: Mike Perham >Assignee: Dennis Lundberg > 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
[jira] Updated: (MCHANGES-50) Handle JIRA authentication failure
[ http://jira.codehaus.org/browse/MCHANGES-50?page=all ] Dennis Lundberg updated MCHANGES-50: Fix Version/s: (was: 2.0-beta-2) > 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 > 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
[jira] Updated: (MCHANGES-50) Handle JIRA authentication failure
[ http://jira.codehaus.org/browse/MCHANGES-50?page=all ] Jochen Wiedmann updated MCHANGES-50: Attachment: MCHANGES-50.tar.gz Mike, I have tried to reproduce your problem, using the attached test project, but could not. Could you please be more specific how to reproduce it? > 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
