Thanks Girish,
Yes, I found that too.
The weird part is if I run "gradlew generateAllPluginsDocumentation" then the
OFBiz-Logo.svg in plugins are deleted. Not when I run any other task.
So it seems that config does not run completely the tasks. But if I put a
println("======================================================================")
just above
doLast { delete "${component}/src/docs/asciidoc/images/OFBiz-Logo.svg" }
Then running any tasks show the println.
So why Gradle does not then run
doLast { delete "${component}/src/docs/asciidoc/images/OFBiz-Logo.svg" }
is still a mystery to me.
Could be the component part missing. But it does not make more sense to me :D
Jacques
Le 27/08/2020 à 12:16, Girish Vasmatkar a écrit :
Hi Jacques -
This explains it nicely -
https://blog.softwaremill.com/my-task-whats-wrong-with-your-gradle-task-82312100c595
Turns out that gradle's configuration phase appears to be "running" the
tasks.
Best,
Girish
On Thu, Aug 27, 2020 at 3:12 PM Jacques Le Roux <
[email protected]> wrote:
Hi,
While looking at this issue I found that a simple "gradlew config"
generates the files which are used by generatePluginDocumentation and
generateAllPluginsDocumentation.
So somehow these tasks are "activated" just launching any task. Does
somebody knows why it's so?
Thanks
Jacques
