Controlling task configuration order
try to register task B on the last steps of task A and like you did make B depend on A tasks.register(“TaskA”) { ext[“TaskAExt”] = SomeImportantObject doLast { tasks.register(“TaskB”) {...
View ArticleLooking for a way to force a task that has no input & output to run again on...
@Lance if Gradle api is not designed to run a task twice per gradle invocation, can you please hint me into a good direction on this question? Force rerun a task by another task I would be very...
View ArticleDefining a composite build only to build all subprojects
@trejkaz try this in your rootproject build script allprojects { it.tasks.register("myTask") { ... } }
View ArticleForce rerun a task by another task
Gradle doesn’t work like this. A task will never run twice in a single Gradle invocation. Instead of trying to execute a single task twice (with different config) you should create two tasks of the...
View ArticleForce rerun a task by another task
@Lance I understood that the hard way, and how gradle works after I saw your comment in the other thread. Let me put some context here: I am developing a gradle plugin that will handle navigation in...
View ArticleForce rerun a task by another task
I’m not familiar with Kotlin but I have a deep understanding of Gradle / Java. i am configuring kapt compiler into these sub projects they will run the task kaptDebugCompile and generate some source...
View ArticleForce rerun a task by another task
@Lance The essence of service sub project is to enable other subproject to know about available destination in different subproject without having to depend on them. So everyone depend on service and...
View ArticleClik here to view.
Force rerun a task by another task
Lance: You could do 5 in the service project. You’d just need to use configurations to break the chicken/egg problem. Perhaps each project has a “generated” configuration. I am pretty interested in...
View ArticleForce rerun a task by another task
You need to break the chicken or egg problem. Use configurations to solve the problem. project(':service') { configurations { allgenerated } dependencies { allgenerated project(path: ':a',...
View ArticleForce rerun a task by another task
@Lance Muchas gracias! I will translate this into java gradle dsl api since i am configuring all subproject from the plugin apply function, and get back to your with a result. Hopefully this will...
View ArticleForce rerun a task by another task
@Lance Unfortunately I am getting this exception A problem occurred evaluating project ':service'. > Could not find method allgenerated() for arguments...
View ArticleForce rerun a task by another task
Did you add this project(':service') { configurations { allgenerated }
View ArticleForce rerun a task by another task
My bad I have declared allGenerated in :service and consumed allgenerated in :a
View ArticleForce rerun a task by another task
Btw you seem to have an amazing understanding of gradle Kuddos!!. Could you please suggest me some resources to understand the usage of artifacts with gradle? the official docs don’t explain in details
View ArticleForce rerun a task by another task
I just start at Project.getArtifacts() which leads to ArtifactsHandler
View ArticleForce rerun a task by another task
I will have a look Thanks a lot. Btw you mentioned earlier that i should create a task that compiles service with different config/dependency. The default task to do that is compileDebugJavaWithJavac...
View ArticleForce rerun a task by another task
Try adding println "***${tasks.compileDebugKotlin.class.name}" You’ll see what task type it is. Or you could go to the android plugin docs which should tell you the type of the task. Then you’ll...
View ArticleForce rerun a task by another task
I executed this CLI command which gives info about the task ./gradlew help --task :service:compileDebugKotlin here is the output: > Task :help Detailed task information for...
View ArticleClik here to view.
Controlling task configuration order
shadowface: try to register task B on the last steps of task A Don’t do this. Gradle has a “configuration” phase and an “execution” phase. A doLast {…} closure is running in the “execution” phase and...
View Article