[#MPJIRA-17] Plugin uses deprecated API to retrieve JIRA issues - jira.codehaus.org

Maven 1.x JIRA Plugin

Plugin uses deprecated API to retrieve JIRA issues

Created: 13/Jan/06 05:09 AM Updated: 13/Jan/06 01:11 PM Resolved: 13/Jan/06 01:11 PM

Return to search

Component/s:

None

Affects Version/s:

1.2

Fix Version/s:

1.3

Time Tracking:

Not Specified

Environment:

JIRA 3.4.1-#107

Description

« Hide

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 ?

Sort Order:

[ Permalink | « Hide ]

Lukas Theussl added a comment - 13/Jan/06 12:19 PM

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.