Good day! I'm started to learn convention plugins ...
# plugin-development
j
Good day! I'm started to learn convention plugins and have some question context: I created convention plugin and on
apply() { }
i register tasks called "deploy" deploy task executes some code checking. Executing it will be:
./gradlew myappname:deploy
I have no issue so far everything it working. When i look at the terminal I wonder why it is calling other projects. Let's say i have other project name
app1
,
app2
,
app3
calling
./gradlew myappname:deploy
results to:
Copy code
> Configure project: app1
> Configure project: app2
> Configure project: app3
> Configure project: myappname
Well I just want to understand what is happening to make a informed decision if I want to pursue this 1. If I have 100 projects, so it will be called right? 2. Is this secure? 3. Am I doing the right thing? 4. Can this be improve?
e
https://docs.gradle.org/current/userguide/multi_project_configuration_and_execution.html#sec:decoupled_projects by default all projects are configured, because Gradle doesn't know if you might have a buildscript in one project whose configuration reaches into and modifies another project
configure on demand was introduced to help with this, but it doesn't prevent cross-project configuration, it just makes the result less predictable :(
the solution to that is project isolation, which is still in the works
j
ohh I see. thank you now I understand