-
Suggestion
-
Resolution: Done
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
In JIRA v5.0 we are creating a separate API module for plugin developers to depend on to give more security that the plugin will remain compatible with future JIRA versions.
Plugins devs can change the dependency on "atlassian-jira" to "jira-api" in their maven pom.xml like so:
<dependency> <groupId>com.atlassian.jira</groupId> <artifactId>jira-api</artifactId> <version>${jira.version}</version> <scope>provided</scope> </dependency>
This issue is intended to gather feedback on what is included and what isn't included, and is of particular interest for JIRA v5.0 Early Access releases (milestones and betas).
- is related to
-
JRACLOUD-22139 Feedback for REST API
- Closed
-
JRASERVER-25596 Feedback for Java API
- Closed
The "class file version" refers to the version of the JDK that was used to compile the class.
The crowd jar is compiled using Java 6 and Bamboo is compiling your code with Java 5, which then is incompatible with the crowd jar.
You need to configure the Bamboo build to use Java 6.