[ http://jira.codehaus.org/browse/MPJIRA-17?page=comments#action_55725 ] 

Lukas Theussl commented on MPJIRA-17:
-------------------------------------

Indeed, the maven-jira-plugin uses the parameters 'resolutionIds', 
'priorityIds' and 'statusIds', which have been deprecated in JIRA 3.3 
(http://confluence.atlassian.com/display/JIRA/Parameter+changes+in+Issue+Navigator).

I will look into it.

> Plugin uses deprecated API to retrieve JIRA issues
> --------------------------------------------------
>
>          Key: MPJIRA-17
>          URL: http://jira.codehaus.org/browse/MPJIRA-17
>      Project: maven-jira-plugin
>         Type: Bug

>     Versions: 1.2
>  Environment: JIRA 3.4.1-#107 
>     Reporter: Silvester van der Bijl
>      Fix For: 1.3

>
>
> Jira is logging errors about a client accessing a deprecated API. We think 
> the JIRA plugin is causing this:
> INFO: 2006-01-12 23:56:31,125 WARN [jira.util.retro.InvalidParamLogger] 
> DEPRECATED. Deprecated parameters called for URL 
> '/secure/IssueNavigator.jspa?view=rss&pid=10001&statusIds=1&status=3&status=4&resolution=-1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=1000&reset=true&decorator=none'
>  from remote user with ip address ............. They should be informed that 
> their bookmark has been deprecated and should be updated.
> It seems a new API is available ? 

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to