The downside of using com.atlassian.jira.jira-core dependency? Edited

When the SDK creates a plugin, it comment the com.atlassian.jira.jira-core dependency:

<!-- Add dependency on jira-core if you want access to JIRA implementation classes as well as the sanctioned API. -->
<!-- This is not normally recommended, but may be required eg when migrating a plugin originally developed against JIRA 4.x -->

Why is this normally not recommended and what are the downsides?

I want to use SelectCFType from it.



1 answer

1 accepted

2 votes
Accepted answer
Gaston Valente Community Champion Jul 23, 2017


Getting that dependency allows your code to reference direct classes at a lower level that the recommended by using services and manager interfaces.

I think that the downside is related to the grade of coupling your code will had with atlassian's api.

Sometimes, if you need to reference concrete classes, for example to inherit from them, this is required.

Just for you to know, i just try to remove this dependency in a custom mail handler i have that uses SelectCFType:


Then i cannot use concrete classes:

Screen Shot 2017-07-23 at 22.29.33.png 


Good answer. Loose coupling always makes sense. Even if the Jira Core classes will not change very frequently. Thx

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

883 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you