_Preamble_: People are usually aware of lifecycle tasks such as

build

,

check

and

assemble

. Although sufficient for smaller projects I have found doing work for a number of organisations that a couple of petterns arise that really need to have additional lifecycle tasks. Having those also means that CI pipeline recipes can be simplified such that the pipelines only have to call the appropriate lifecycle tasks. Build script and plugin authors can then focus on adding the appropriate tasks into these lifecycle tasks. Anyhow, I finally got fed up, having to recreate similar setups, so I created a lightweight set of plugins that can be reused and hopefully be some standardisation for people. Obviously if you have already done something like this in your organisation, you have no need for this, but if you are building from scratch again or would like for standard, this could be helpful to you. I've setup it up in such a way that you can take all of the lifecycle tasks, or just a subset. There is seven lifecycle tasks in this release. Feel free to discuss or contribute more if you want. gradle-lifecycles.ysb33r.org/lifecycle-tasks/1.0.1/tasks.html

I usually have a

generate

task, so that all generated code and resources can be triggered. This can be used manually after a fresh checkout or clean and I usually also wire that into IDE sync, for example using the

idea-ext

plugin.

That's a neat idea.

Huge +1 about

generate

What would consider the relationship to be between

assemble

and

generate

? • 0️⃣ None • ⛓️

assemble.dependsOn("generate")

• 🏃

assemble.mustRunAfter("generate")

I usually have none. For me it is as after-sync task for

idea-ext

and for manual usage.

I added

generate

to the Lifecycles plugin (v1.1.0) with no relation to

assemble

.