[GRADLE-2750] Obtaining maven-style coordinates for published artifacts via tooling API Created: 12/Apr/13  Updated: 02/Oct/14  Resolved: 06/Apr/14

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.12-rc-1

Type: New Feature
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Fixed Votes: 17


It would be useful for tools like STS/Idea to be able to obtain information such as the maven-style coordinates of the artifacts that a given project produces.

One important use case is the automatic remapping of jar dependencies to project-level Gradle -> Gradle dependencies in the workspace.

See https://issuetracker.springsource.com/browse/STS-2834

Related discussion:


Comment by Gethin James [ 08/May/13 ]

Any plans/timescale to implement this?

Comment by Adam Murdoch [ 08/May/13 ]

We do plan to implement this, it's just a matter of finding the time. It is something we'd welcome a community contribution for (same with anything else missing from the tooling API models), if anyone wants to help out with this.

Comment by Lance S [ 21/May/13 ]

I'm interested in helping out with this but I'm unfamiliar with the gradle source code. Can a gradle guru point me in the right direction as to which classes are likely to be involved and a general overview of the solution?

Comment by Adam Murdoch [ 24/May/13 ]

@Lance, thanks for your offer to help. I've added some suggestions for implementing this to the tooling API design spec: https://github.com/gradle/gradle/blob/master/design-docs/tooling-api-improvements.md#story-expose-the-publications-of-a-project

You'd just need to implement the first story listed in the spec (ignore all the other stuff). Please ask on the dev mailing list if you have questions, or if you want to discuss the implementation.

Comment by Lance S [ 04/Oct/13 ]

Just a quick update to say I won't be fixing this issue. I've moved teams and I'm no longer using Gradle.

Comment by Adam Murdoch [ 16/Oct/13 ]

Thanks for letting us know

Comment by Chris Dore [ 01/Oct/14 ]

What is the best way for me to find out what was implemented in order to resolve this issue? I'd like to get some more information on how it works and how it can be used.

Comment by Lance S [ 02/Oct/14 ]

Here's some docs

Generated at Wed Jun 30 12:30:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.