Enhancing plugin with a possibility to detect relationship between generated artifacts and Eclipse Gradle projects

[romix]

I have the following setup:

• N Gradle (root )projects A1..An, each imported in Eclipse as a separate project
• Some of the Gradle projects are dependent on artifacts (JARs) produced by other projects (they depend on snapshot versions), e.g. A1 is dependent on the artifact A2-SNAPSHOT.jar produced by A2.

When I change sources in A2 and add e.g. a new method, I'd like to be able to directly use this new method in A1, i.e. with autocompletion, etc. But today it is not possible, because this change is invisible to Eclipse. One should first build and locally deploy the artifact produced by A2. And only then Eclipse detects the change in the JAR and is able to provide autocompletion and so on.

It would be nice, if Eclipse could detect this kind of changes automatically without requiring a dedicated build/local deploy step. It would be much more convenient and less error-prone.

Idea: I can imagine that this feature would work, if the Eclipse project for A1 would depend on the Eclipse project for A2 (and with current Gradle Plugin and Gradle tooling it always depends on the JAR produced by A2 and therefore changes are not detected automatically). So, a possible solution could be that Gradle plugin detects that a given JAR is produced by a given Eclipse Gradle project and adds the dependency on that project automatically in the Eclipse project configuration.

What do you think?

[BoykoAlex]

Think it makes sense. Can you please submit a JIRA for this enhancement? (Would be nice if you could attach a sample project to the JIRA)

On May 28, 2014, at 5:17, romix notifications@github.com wrote:

I have the following setup:

N Gradle (root )projects A1..An, each imported in Eclipse as a separate project
Some of the Gradle projects are dependent on artifacts (JARs) produced by other projects (they depend on snapshot versions), e.g. A1 is dependent on the artifact A2-SNAPSHOT.jar produced by A2.
When I change sources in A2 and add e.g. a new method, I'd like to be able to directly use this new method in A1, i.e. with autocompletion, etc. But today it is not possible, because this change is invisible to Eclipse. One should first build and locally deploy the artifact produced by A2. And only then Eclipse detects the change in the JAR and is able to provide autocompletion and so on.

It would be nice, if Eclipse could detect this kind of changes automatically without requiring a dedicated build/local deploy step. It would be much more convenient and less error-prone.

Idea: I can imagine that this feature would work, if the Eclipse project for A1 would depend on the Eclipse project for A2 (and with current Gradle Plugin and Gradle tooling it always depends on the JAR produced by A2 and therefore changes are not detected automatically). So, a possible solution could be that Gradle plugin detects that a given JAR is produced by a given Eclipse Gradle project and adds the dependency on that project automatically in the Eclipse project configuration.

What do you think?

—
Reply to this email directly or view it on GitHub.

[thomasj003]

Just took the liberty to do that --> https://issuetracker.springsource.com/browse/STS-3837 as I would love to see that feature in place as well.

Note: romix and me don't know each other, just seem to have the same problems / ideas ;)

[romix]

@thomasj003 Thanks a lot for submitting a JIRA issue for this enhancement! You saved my time.

[thomasj003]

You might want to vote on the issue to show that more people are interested :)

[romix]

Done

[kdvolder]

Duplicate of: https://issuetracker.springsource.com/browse/STS-2834