How to include Apache Poi dependency in Jira Plugin ?

[Albert Cameron]

Just putting this dependeny in the pom.xml file of a Jira Plugin crashes the whole application:

<dependency>
     <groupId>org.apache.poi</groupId>
     <artifactId>poi-ooxml</artifactId>
     <version>5.0.0</version>
 </dependency>

 First it says :

Failed to execute goal com.atlassian.maven.plugins:jira-maven-plugin:8.1.0:validate-banned-dependencies (default-validate-banned-dependencies) on project aanf-transformer: Some Enforcer rules have failed.

Why is this happening. I cannot execute lifecycle mvn install 

[Nhac Tat Nguyen]

@Albert Cameron The error message tells everything, version 5.0.0 has some banned dependencies, and it did not pass the verification.

[Nhac Tat Nguyen]

Please downgrade to the version 4.x.x. This works for me on Jira Server 8.13.4

<dependency>
  <groupId>org.apache.poi</groupId>
  <artifactId>poi-ooxml</artifactId>
  <version>4.1.2</version>
</dependency>

[Albert Cameron]

Wow amazing :) At least I can package it now :) What could be reason 

<version>5.0.0</version>

 is not working. But really thanks :)

[Albert Cameron]

When I upload it unfortunately I get another error:

Caused by: org.osgi.framework.BundleException: Unable to resolve de.myCompany.area27.myPlugin [269](R 269.0): missing requirement [de.myCompany.area27.myPlugin [269](R 269.0)] osgi.wiring.package; (osgi.wiring.package=com.github.luben.zstd) Unresolved requirements: [[de.myCompany.area27.myPlugin [269](R 269.0)] osgi.wiring.package;

[Nhac Tat Nguyen]

If you open the pom.xml file, you will see the <import-package>. Please add the text ;resolution:="optional" after the symbol * as in the code.

<Import-Package>
  org.springframework.osgi.*;resolution:="optional",
  org.eclipse.gemini.blueprint.*;resolution:="optional",
  *;resolution:="optional"
</Import-Package>

[Albert Cameron]

wow. cool . It looks like the last line *;resolution:="optional"  made the difference . All the other was already in my pom.xml .

This is some configuration from the  jira-maven-plugin which caused all the trouble. Thanks a lot :)