Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

what Jira Java REST client should I use

Jorge Amat April 9, 2018

When I look for a jira java rest client, I find that I can use one of the following options available:

Atlassian JIRA REST Java Client » 2.0.0-m2:

https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client/2.0.0-m2

(last update done from Dec 2012)

or

JIRA REST Java Client Implementation » 5.0.4

https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client-core/5.0.4

along with

JIRA REST Java Client Public API » 5.0.4

https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client-api/5.0.4

(last update done from Dec 2017 for both)

 

In principle, the jira-rest-java-client is more easy and clear to use and I just need to add only one dependency to my project, however:

Is there any actual difference between the two options, despite the last date update provided by maven? 

I have checked that in both cases you cannot create a Project, despite it is possible based on https://docs.atlassian.com/jira/REST/7.0.0-m01b/#api/2/project-createProject

What option should I go for?

 

2 answers

1 vote
Jakub Sławiński
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 4, 2019

Hi @Jorge Amat

 

you should use the newest JIRA REST Java Client Implementation, i.e.  https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client-core/5.1.0

 

 

Regards,

  Jakub.

Oleksandr Shkurat
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 8, 2019

Hello Jakub.

Have you seen the issue https://ecosystem.atlassian.net/browse/JRJC-149 ?

After six years it's still not fixed. I totally disagree with its minor priority as long as it totally blocks any kind of using a client API.

I've read about a number of workarounds including modifying JAR manually right inside local Maven repo, however I guess it's a shame for a such big company as Atlassian to react so lazily. 

The solution is described here:

https://community.atlassian.com/t5/Answers-Developer-Questions/Java-Jira-REST-API-connect-problem/qaq-p/541518

there is even a pull request made by a community
https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/92
However it looks like it is not valid.

Could you please push this problem to make your API client finally working?

 

Best regards,

Oleksandr.

0 votes
Edwin Kyalangalilwa
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 17, 2019

Hi @Jorge Amat,

I've seen lots of developers utilizing creating their own URI's.

For example:

String projectURI = "/rest/api/2/project/" + projectIdOrKey + ... );

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, loom, loom for training, loom for teaching, video training, async learning, online education, screen recording, loom tutorials, loom use cases, atlassian learning, team training tools, instructional video, virtual training tools

🛗 Elevate Your Training and Enablement with Loom

Join us June 26, 11am PT for a webinar with Atlassian Champion Robert Hean & Loom’s Brittany Soinski. Hear tips, stories, and get your burning questions answered. Learn how Loom makes training and enablement easier. Don’t miss it!

Register today
AUG Leaders

Atlassian Community Events