Plugin seems to determine all inputs during project configuration. At that time not all diagrams might be already existing. Some diagrams might be generated by other tasks run before plantUml task. Unfortunately, plantUml does not see such diagrams (because they do not exist yet during project configuration) and report their absence. Workaround is to build second time without clean so that plugin sees the diagrams during configuration phase. Instead, plantUml task should use usual gradle api for inputs which dynamically discovers files to operate on when the task is actually called.
You can see scan of first build here:
https://scans.gradle.com/s/acg3fca45mwea/console-log
And scan of second build without clean here:
https://scans.gradle.com/s/l2armzps356fa/console-log
These scans were generated for the following config where build/all-sprites.puml is a diagram generated during build:
Plugin seems to determine all inputs during project configuration. At that time not all diagrams might be already existing. Some diagrams might be generated by other tasks run before
plantUm
l task. Unfortunately,plantUml
does not see such diagrams (because they do not exist yet during project configuration) and report their absence. Workaround is to build second time without clean so that plugin sees the diagrams during configuration phase. Instead,plantUml
task should use usual gradle api for inputs which dynamically discovers files to operate on when the task is actually called. You can see scan of first build here: https://scans.gradle.com/s/acg3fca45mwea/console-log And scan of second build withoutclean
here: https://scans.gradle.com/s/l2armzps356fa/console-logThese scans were generated for the following config where
build/all-sprites.puml
is a diagram generated during build: