nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why am I getting "Unresolved constraint in bundle" exceptions after I migrated development environment to support JIRA7

Tuncay Senturk _Snapbytes_

Hi there,

I am in the process of migrating my JIRA add-on to JIRA 7.x

However I am facing weird issues, one of them is as below:

[INFO] [talledLocalContainer] Caused by: org.osgi.framework.BundleException:
Unresolved constraint in bundle com.mycompany.helloworld [192]: 
Unable to resolve 192.0: missing requirement [192.0] 
osgi.wiring.package;
(osgi.wiring.package=com.atlassian.plugin.spring.scanner.annotation.export)

Any comments?

Thanks

Accepted answers

Tuncay Senturk _Snapbytes_

I added following Import-Package lines to pom.xml. Saved my life

&lt;Import-Package&gt;
	javax.ws.rs*;version="[1,2)",	
	javax.servlet*;version="2.5",
	javax.xml.bind*;version="[2.1,3)",
	*;version="0";resolution:=optional
&lt;/Import-Package&gt;

All comments

Tim Eddelbüttel

I got the same within a Confluence Space Blueprint with the latest SDK.

Tuncay Senturk _Snapbytes_

I added following Import-Package lines to pom.xml. Saved my life

&lt;Import-Package&gt;
	javax.ws.rs*;version="[1,2)",	
	javax.servlet*;version="2.5",
	javax.xml.bind*;version="[2.1,3)",
	*;version="0";resolution:=optional
&lt;/Import-Package&gt;

Alok Singh2

I am also getting this error Getting Unresolved constraint in bundle Unable to resolve 178.0: missing requirement [178.0] osgi.wiring.package; (&(osgi.wiring.package=com.atlassian.activeobjects.external)(version>=0.23.0)(!(version>=1.0.0))) while compiling the plugin on JIRA-7 I tried the above solution but it is generating IDE error.

Koen Martens

Got this when following the JIRA plugin tutorial (https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project/put-the-final-polish-on-the-project-in-eclipse). Nice introduction to JIRA plugin development ......

edit

Note to self or others who run into this: delete the target directory under your helloWorld plugin project, and it works fine again (just takes a long time to repopulate target).

Martin Simoneau1

Delete the target directory saved my day.

Thanks Koen !

nelswadycki

@Tuncay Senturk [Snapbytes] - How did you figure out which packages to add to the Import-Package definition?

com.atlassian.plugin.spring.scanner.annotation.export seems very unrelated to the packages that you ended up adding.

Tuncay Senturk _Snapbytes_

It has been while and I do not remember all steps. I'm not sure but the last line (including star) might do the trick.

Scott Wilson_nx59bv

THis may work for helloworld, and initially for the MyPluginServlet part of the tutorial, but it fails when you try to run the servlet. I would be ashamed of my work if I was tasked with writing this plugin documentation!!!!!

unknown

I am facing the same error, missing package com.atlassian.plugin.spring.scanner.annotation.export. It is really funny since I have checked over and over again that it is correctly declared as a dependency on the project's pom.xml and that it has been correctly downloaded to the project's local repository.

Anyone could help me? Since JIRA 7 appeared, add-on development is a hell. Instead of JIRA showing normal errors that can be fixed by the add-on developer, it seems that it "invents" senseless errors that are not related to anything that could be happening actually.

;version="0";resolution:=optional

Nabil Sayegh

Try

atlas-mvn clean

wink

Roman Samorodov

Doesn't help me. This command just delete "target" folder.

Roman Samorodov

Add-on development is a hell...True true/

Nabil Sayegh

It helps every single time here, especially when upgrading sdk/amps or dependencies.

Claus Gerull

Helped me too with an "Unable to resolve 161.0: missing requirement ..." OSGI error.

dralexk

I have found a solution in https://bitbucket.org/atlassian/atlassian-spring-scanner.

In the dependencies section, make sure that the scope of the following is provided.

&lt;dependency&gt;
            &lt;groupId&gt;com.atlassian.plugin&lt;/groupId&gt;
            &lt;artifactId&gt;atlassian-spring-scanner-annotation&lt;/artifactId&gt;
            &lt;version&gt;${atlassian.spring.scanner.version}&lt;/version&gt;
            &lt;scope&gt;provided&lt;/scope&gt;
        &lt;/dependency&gt;

Alok_dw9ego

Thanks, this saved me big time. I forgot the concept of maven dependency mechanism and I spent almost like 1 hour to fix this problem and suddenly I saw this.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-development

jira-core

upgrade

osgi