Missing artifacts in Atlassian repo

[Yuri Ushakov]

Hi, I added jira-api dependency in my project, and SBT cannot resolve three artifacts:

1. jta:jta:1.0.1 (it's not in the Atlassian public repo indeed. The directory is there, but it's empty. And repo1.maven.org has only 1.0.1b version.)

2. com.atlassian.sal#sal-api;2.8.0-m2!sal-api.atlassian-plugin

3. com.atlassian.gadgets#atlassian-gadgets-api;3.2.0-m2-1!atlassian-gadgets-api.atlassian-plugin

For 2 and 3, it looks for .atlassian-plugin for some reason, not .pom files. But .atlassian-plugin files are missing from the Atlassian repo as well.

Googling for it yielded no results, except that people tend to use some customized Atlassian's maven or something.

Is there an easy to way to make those artifacts resolve?

Thanks.

Upd: 5.2.0 and 5.2.11 both have this problem.

[Yuri Ushakov · Accepted solution]

I think it's an SBT problem, and I believe SBT uses Ivy. The same dependency resolves perfectly with stock Maven 3.0.4.

[Andy Brook [Plugin People]]

Hi Yuri, some libaries like JTA have licensing restrictions, go download from:

- http://download.oracle.com/otndocs/jcp/7287-jta-1.0.1a-class-oth-JSpec/?submit=Download

And install with mvn tool

- http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html

As for the others, failed dependencies happen from time to time, a parent pom refering to an RC that never got published is on possibility. Unless you actually need to use the libraries concerned, you can also just exclude them in your pom

- http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

If you really want them, you could dig for the nearest available version via:

- https://maven.atlassian.com/content/groups/public/com/atlassian/jira/

[Yuri Ushakov]

I can understand JTA, but the other artifacts? So what you're saying yes, it's broken, and there's nothing I do wrong or can do except exclude. That's something, thanks.

[Andy Brook [Plugin People]]

All I can say is I dont have the problem you see, likely it will relate to your chosen parent pom with defined versions therein. If you 'just' depend on jira-api you shouldn't see this as final releases do not (should not!) have non-final (eg milestone) dependencies, which is what you can't find...

[Yuri Ushakov]

5.2.0 and 5.2.11 both have this problem.

[Boris Georgiev _Appfire_]

Which version of jira-api you depend on ?