Find Questions…

Close ×
First time here? Check out the FAQ!

Jira 4.4.4 : SearchParameter.java doesn't exist

mijil das asked this question · 20 karma ·

I am upgrading from jira 4.1.1 to 4.4.4, currently looking at configuring custom field, the error log says

2012-01-16 05:02:04,228 main ERROR [com.atlassian.jira.ComponentManager] Error occurred while starting component 'com.atlassian.jira.event.DefaultListenerManager'.
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NoSuchMethodError: com.atlassian.jira.util.EasyList.build([Ljava/lang/Object;)Ljava/util/List;
****************************************************

The following plugins failed to load:
Escalate Jira Reports Package: There was a problem loading the descriptor for module '***Fix Resolution Date' in plugin 'Escalate Jira Reports Package'.
Error retrieving dependency of class: com.escalateretail.reports.FixResolutionDateReport. Missing class: com/atlassian/jira/issue/search/SearchParameter
****************************************************

Please advice.

Thank you,
Mijil

541 views

mijil das · 20 karma ·

Still not resolved, please advice me based on the code given by.

2 Answers:

Jamie Echlin · 48,949 karma ·

You need to rewrite your queries using eg jql query builder:

JqlQueryBuilder jqlQueryBuilder = JqlQueryBuilder.newBuilder()
Query query = jqlQueryBuilder.where().project(projectId).buildQuery()

mijil das · 20 karma ·

which file do i need to add. My searchparameter.java contains, im trying to configure custom field from a custom jar file which works fine in jira 4.1.1

public interface SearchParameter
{
/**
* Adds a given value to the list of values
*
* @param value value to add
*/
void addValue(Object value);

/**
* Returns a list of values
*
* @return list of values
*/
List getValues();

/**
* Get issue field name.
*
* @return issue field name
*/
String getName();

/**
* Specify issue field name to limit search by. Either a predefined name (from
* {@link com.atlassian.jira.issue.IssueFieldConstants}, or
* {@link com.atlassian.jira.issue.fields.CustomField#getId()}.
*
* @param fieldname field name
*/
void setName(String fieldname);

/**
* Return an XML elemnt representation of this search parameter.
*
* @return XML element
*/
Element getXml();

/**
* Initialise this search parameter using an XML element.
* <p/>
* Usual process is:
* <pre>
* SearchParameter param = new MySearchParameter();
* param.setXml(element);
* </pre>
*
* @param el XML element
*/
void setXml(Element el);

/**
* Returns true if this parameter is valid, false otherwise.
*
* @return true if valid, false otherwise
*/
boolean isValid();

/**
* Returns the query string
*
* @return query string
*/
String getQueryString();

}

String getQueryString();
}

Thanks

Jozef Kotlár · 2,673 karma ·

SearchParameter was removed from API in version 4.0+. There are upgrade notes for developers explaining steps you need to make.

In JIRA 3.x and earlier, searching was achieved using a SearchRequest in combination with SearchParameters and SearchSorts. While the SearchRequest still continues to exist in JIRA 4.0, the SearchParameters have been replaced with the Query object.

Jamie is right - you need to rewrite your queries using JQL. It is strange, that the plugin has worked in version 4.1.

Looking for something else?

Find Questions…

or Browse other questions tagged:

or Ask a Question