Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
4.0
-
4
-
Description
Hi,
I'm trying to migrate a custom fields made in jira 3.13 to jira 4.0 but I have a problem with its custom field searcher.
I use the following code in atlassian-plugin.xml (this code comes from system-customfieldtypes-plugin.xml which is part of jira source code)
<customfield-searcher key="exactnumber2" name="Number Searcher" i18n-name-key="admin.customfield.searcher.exactnumber.name" class="com.atlassian.jira.issue.customfields.searchers.ExactNumberSearcher"> <description key="admin.customfield.searcher.exactnumber.desc">Allow searching for a number which exactly matches.</description> <resource type="velocity" name="search" location="templates/plugins/fields/edit-searcher/search-basictext.vm"/> <resource type="velocity" name="view" location="templates/plugins/fields/view-searcher/view-searcher-basictext.vm"/> <valid-customfield-type package="com.atlassian.jira.plugin.system.customfieldtypes" key="float"/> <valid-customfield-type package="com.atlassian.jira.plugin.system.customfieldtypes" key="importid"/> <valid-customfield-type package="org.hakanai.jira.plugins.order.core" key="ordertype"/> </customfield-searcher>
However I always have the following error :
2009-11-20 20:33:19,767 http-8080-Processor24 ERROR hugo 73999x18x1 1qu0oyr http://localhost:8080/secure/admin/CreateCustomField.jspa [atlassian.plugin.manager.DefaultPluginManager] Exception when retrieving plugin module exactnumber, will disable plugin org.hakanai.jira.plugins.jira-order-plugin
com.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.atlassian.jira.issue.customfields.searchers.ExactNumberSearcher': Unsatisfied dependency expressed through constructor argument with index 0 of type [com.atlassian.jira.web.FieldVisibilityManager]: : No unique bean of type [com.atlassian.jira.web.FieldVisibilityManager] is defined: Unsatisfied dependency of type [interface com.atlassian.jira.web.FieldVisibilityManager]: expected at least 1 matching bean; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.atlassian.jira.web.FieldVisibilityManager] is defined: Unsatisfied dependency of type [interface com.atlassian.jira.web.FieldVisibilityManager]: expected at least 1 matching bean
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)
at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:115)
at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:73)
at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.getModule(JiraResourcedModuleDescriptor.java:124)
it seems to be related with JRA-18431 , JRA-18008, GHS-1394 but according to JRA-18431 it should be fixed now.
In jira source code ExactNumberSearcher is using an interface and not a concrete implementation.
So I don't understand, is FieldVisibilityManager available for OSGI plugins (v2 plugins) ?