maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MCHANGES-50) Handle JIRA authentication failure
Date Thu, 02 Aug 2007 19:31:13 GMT

     [ http://jira.codehaus.org/browse/MCHANGES-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dennis Lundberg closed MCHANGES-50.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta-3

It turns out that my test project was busted in other respects. After fixing that I now get
a pretty "empty" report that says that an error occurred and directing to the console for
more info.

> 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
>             Fix For: 2.0-beta-3
>
>         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