maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCHANGES-50) Handle JIRA authentication failure
Date Wed, 26 Jul 2006 06:09:23 GMT
    [ http://jira.codehaus.org/browse/MCHANGES-50?page=comments#action_70708 ] 
            
Jochen Wiedmann commented on MCHANGES-50:
-----------------------------------------

Mike, are you sure about the 500 error? If so, then Jira behaves very unfortunate, as 500
is "Internal Server Error", which is more than unusual for authentication requests. Besides,
please note that I could not find any problems with http://jira.webifysolutions.com/ as a
Jira server. (See the attached test project.)


> 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

        

Mime
View raw message