Run tasks on synchronization

[donat]

Motivation

Some projects have setup tasks that need to be run before they can be used in the IDE. That might be a long-running code generator or some configuration task for an Eclipse plugin that Buildship has no model for.

This would be an inexpensive workaround for our missing WTP support. Instead of creating a full-blown tooling model for WTP, we could just run the wtpComponent and wtpFacets tasks.

Proposed Change

Add eclipse.synchronizationTasks to the Gradle Eclipse API, expose them via the TAPI and run them before the actual project synchronization.

[donat]

Comment by oehme
Monday Aug 29, 2016 at 09:02 GMT

---

The WTP case can be implemented even simpler by hardcoding support as in #85 .

[donat]

Related issue in Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510331

[adammurdoch]

It would be nice if we solved this by offering a way to declare the developer inputs in a Gradle build definition, and simply make sure these things are built on import and then kept up-to-date as things change. This way, the inputs can be made usable regardless of which IDE the developer is using.

We might model these as 'buildable things' somewhere that you declare, or we might infer that generated source files or resources that are inputs into the main or test source sets should be built prior to use from the IDE.

[oehme]

@adammurdoch this ticket is more about Eclipse-specific things that need to be generated when you "sync" the Eclipse configuration. This is really just a convenience for Gradle plugins that don't want to build a full-blown tooling model + Eclipse plugin, but just want to create some configuration file.

There is another ticket (#266) for what you are referring to: Tasks that need to be run in order to keep generated sources up-to-date. These should be IDE independent, but I don't think we're there yet: We want to replace the built-in generators/compilers in IDEs, but that requires us to provide the same rich diagnostics that IDEs currently provide (e.g. collecting all errors and warnings from all generators/compilers and putting them on the correct source files). Of course doing exactly that could be the solution for #266 instead of having an Eclipse-specific list of tasks.

[Kameecoding]

what's the status of this feature is it being worked on?

[ChristianCiach]

We need this to automatically trigger eclipseFactorypath and eclipstJdtApt of the APT-Plugin. There is no way that I convince all my colleagues to manually run these tasks every time the factory path changes.