Can we execute any Gradle script code before/after any Eclipse incremental or full build lifecycle?
I’m used to be able to workaround bug like GRADLE-1275 when using Maven in Eclipse using WTP m2e Eclipse integration. In the Maven world I can decide to run or not run any of the steps when in Eclipse, and we have a way to “prepare” files to be used when doing unpackaged deployment to the web or app server running in Eclipse, using or not “Serve modules without publishing”.
The following is the list of steps in Maven -> https://docs.sonatype.org/display/M2ECLIPSE/Project+build+lifecycle+mapping#Projectbuildlifecyclemapping-Introducenotionsof"interesting"and"notinteresting"mojoexecutions
What can I do in Gradle-Eclipse integration so that some of the file like MANIFEST are “prepared” before been made available to the web/app server running in Eclipse?