This message was deleted.
# community-support
s
This message was deleted.
v
You probably need to show what you tried, because it is pretty unclear. Especially what you mean with CLI vs. "part of build.gradle". If you run a task from CLI it also just executes what you define accordingly in
build.gradle
. And another thing that does not match is, that you speak of "calling a task in build.gradle", because you cannot call tasks. You define tasks and you define dependencies between tasks. So it is most probably that you got some Gradle principle wrong. Please show what you tried and what you do exactly where the behavior is not what you expect.
n
Sorry if my question was confusing. So right now, my build.gradle looks something like this
Copy code
buildscript {
…
}

intellij {

patchPluginXml {
  version.set("<http://xxx.xxx|xxx.xxx>")
}

runPluginVerifier {
	println("Inside runPluginVerifier")
	distributionFile.set(file("path"/to/plugin/artifact.zip))
}
}
When I build the wrapper and my project, the build script is executed successfully with the println statement in the console. But it doesn’t generate any report folders. But when I execute the command ./gradlew runPluginVerifier, it will run with the default options and generate the expected report folders.
v
Actually, configuring the tasks within the
intellij { ... }
block is little helpful. It should be outside the block as there it belongs. Having it inside is just doing nothing and just confusing readers. Besides that, it is still unclear to me what you are doing where it does not behave as expected. You say when you call the task, it is executed as expected but with default values, not with what you configured. You say when you do <what?> you expect it to be executed, but it is not, but that the
println
is shown. Actually, I would say, that the
println
is always shown as you work against task-configuration avoidance. But that if the task is executed, it should use your configured values. It is still unclear to me what you do when you expect the task to be run but it is not. Also, you just set the
distributionFile
property of that task, you do not in any way change when or under which conditions it will be executed.