Really great to see this. I'll add an note about our historical IvyDE usage that is related to this, and then defer to you on whether you'd like to promote it to an issue:
- When we would have, say, 20-30 projects checked out locally, but only, say, 5 of them open in Eclipse (because they're the only ones I'm focused/working on right now), IvyDE would hook up the Eclipse projects of whatever we had open.
- Now let's say I open another one of our projects in Eclipse. Potentially all 5 of the already-open projects in Eclipse could be referencing this project as the jar artifact (from when it was closed) and now should reference the newly-opened project.
- Similarly, if I close a project, all of my still-open projects may refer to a now-closed project, and need to switch back to using a jar form.
In IvyDE, there were two ways of doing this: 1) you could turn on "any time I open/close a project, automatically refresh the deps of all open projects" or 2) they provided a "Resolve All" button that would run "Refresh Deps" for all open projects in Eclipse.
AFAIU (sorry if I've missed this?) right now in Gradle STS, I'd have to go click "Refresh Deps" for each open project? This seems tedious and error prone. Perhaps Gradle STS could have something similar to IvyDE's either automatically- or manually-triggered "refresh deps across all projects"? (Gradle is likely sufficiently faster than Ivy/IvyDE that just doing it automatically all the time would likely be preferable/not noticeable.)
If this already "just works" in 3.6.3, I apologize, I am still on 3.6.2 and so am making assumptions about how this works today.