You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to support isolated projects. To achieve this, we are migrating our project to isolated projects to enable our integration tests with isolated projects to run successfully. We have normal modules and include build modules:
roborazzi
include-build
roborazzi-plugin
roborazzi-core
We have some common logic to set up the JDK and publish libraries for each module using allProjects. It might be challenging to maintain common logic because we already use include-build. I think I would prefer having publish.gradle and jdk-setup.gradle, and using apply from: 'publish.gradle' to copy and paste all the scripts. I am aware that this has performance drawbacks. Is there any way to improve this? I think it is better than nothing.
We would like to support isolated projects. To achieve this, we are migrating our project to isolated projects to enable our integration tests with isolated projects to run successfully. We have normal modules and include build modules:
We have some common logic to set up the JDK and publish libraries for each module using
allProjects
. It might be challenging to maintain common logic because we already use include-build. I think I would prefer havingpublish.gradle
andjdk-setup.gradle
, and usingapply from: 'publish.gradle'
to copy and paste all the scripts. I am aware that this has performance drawbacks. Is there any way to improve this? I think it is better than nothing.https://github.com/takahirom/roborazzi/blob/main/build.gradle#L16
#497 (comment)
The text was updated successfully, but these errors were encountered: