But maven is complaining, that it does not know “import”.
[WARNING] 'dependencies.dependency.scope' for com.atlassian.jira:jira-api-bom:pom must be one of [provided, compile, runtime, test, system] but is 'import'. @ line 23, column 14
Also for other dependencies scope provided should be used, omitting version specifications.
But also here maven is complaining and reminds me to add version number.
Thank you! Okay, now maven doesn’t complain. But now atlas-run fails with compile errors because certain libraries seems not to be found e.g. javax.ws.rs.
It looks like Maven doesn’t recognize the import scope for dependencies. To resolve this, you should place the import dependency inside the dependencyManagement section of your pom.xml. Here’s how you can update your pom.xml:
For the other dependencies, you can keep the provided scope but you might still need to specify the version numbers to avoid Maven warnings. Here’s an updated example:
<dependencies>
<dependency>
<groupId>com.atlassian.jira</groupId>
<artifactId>jira-core</artifactId>
<version>10.0.0</version> <!-- Specify the version number -->
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.4</version>
<scope>provided</scope>
</dependency>
<!-- Add other dependencies similarly -->
</dependencies>
Forthermore with the Jira 10.x comes Java17.
Java 17 has moved many javax packages to jakarta as part of the transition to Jakarta EE2.
Make sure to replace all javax dependencies with their jakarta counterparts. This should help resolve the compatibility issues you’re facing.
You do not have any version inside your definition. You have to declare a version of the package you want to use: