Plugin fails to start with exception Jira 7.1.7

[Owen Marshall]

Hi

Token plugin is failing start after we updated it to latest, we are using Jira 7.1.7

ns-key [c.a.plugin.impl.AbstractPlugin] Because of this exception
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.wombatscorp.jira-tokens
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:419)
at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:286)
at com.atlassian.plugin.manager.PluginEnabler.actualEnable(PluginEnabler.java:130)
at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:107)
at com.atlassian.plugin.manager.PluginEnabler.enableAllRecursively(PluginEnabler.java:79)
at com.atlassian.plugin.manager.DefaultPluginManager.enablePlugins(DefaultPluginManager.java:1657)
at com.atlassian.jira.plugin.JiraPluginManager.enablePlugins(JiraPluginManager.java:131)
... 3 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
at com.sun.proxy.$Proxy138.enablePlugins(Unknown Source)
... 3 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLIntercept

‌

Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.wombatscorp.jira-tokens [192]: Unable to resolve 192.0: missing requirement [192.0] osgi.wiring.package; (osgi.wiring.package=com.atlassian.plugin.spring.scanner.annotation.imports)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3974)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2037)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:400)
2020-02-14 16:35:32,869 http-nio-8080-exec-18 WARN cmarraffa 995x1200031x1 j7rdqn 46.30.55.66,7.0.0.6,7.0.1.51 /brow

[Roma Bubyakin [Wombats Corp]]

Hello @Owen Marshall ,

I’m sorry that you are faced with such issue and already looking into it.

Could you please confirm that you are using “API Tokens for Jira” v1.1.3?

[Owen Marshall]

Hi Roman , v1.1.3is installed,

Thank you Owen

[Roma Bubyakin [Wombats Corp]]

Hi @Owen Marshall

Sorry for the delay.

I was trying to bring compatibility back to 7.0-7.1, but unsuccessfully.

‌

Let me explain some details:

Issue related to v1.1.3 update that fixed Issue #9 and Issue #10.

The fix appears unsupported in the oldest version and I missed that.

That’s why I have to update compatibility for v1.1.3 from 7.2.0.

‌

From the other side you can still use v1.1.1 until next Jira upgrade because it has no other updates than fixes for new Jira versions.

‌

Let me know if I can be helpful somehow,

Roman

[Roma Bubyakin [Wombats Corp]]

Updated compatibility for API Tokens for Jira v1.1.3

[Owen Marshall]

Hi Roma,

After uninstalling and installing again the plugin is now functional again

Thanks you Owen