-
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
[JRACLOUD-25596] Feedback for Java API
Workflow | Original: JAC Suggestion Workflow [ 3142221 ] | New: JAC Suggestion Workflow 3 [ 3637710 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339193 ] | New: JAC Suggestion Workflow [ 3142221 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Component/s | New: Ecosystem [ 53294 ] | |
Component/s | Original: Ecosystem - Java API [ 46588 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2103000 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339193 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2065632 ] | New: JIRA Bug Workflow w Kanban v6 [ 2103000 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1835195 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2065632 ] |
Description |
Original:
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: {code} <dependency> <groupId>com.atlassian.jira</groupId> <artifactId>jira-api</artifactId> <version>${jira.version}</version> <scope>provided</scope> </dependency> {code} 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). |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-25596]. {panel} 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: {code} <dependency> <groupId>com.atlassian.jira</groupId> <artifactId>jira-api</artifactId> <version>${jira.version}</version> <scope>provided</scope> </dependency> {code} 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). |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |