multi-project

Gradle nested multi-projects with project compile dependencies

别说谁变了你拦得住时间么 提交于 2019-11-29 01:06:13
I have an identical problem to this Gradle Multi-Module Project Setup but I have to use project compile dependencies to build and cannot use the library(jar) dependencies solution that was given as a solution in the above question. Root |__ P1 | |_ PP1 | |_ PP2 | |__ P2 |_PP3 |_PP4 PP1, PP2, PP3 and PP4 are sub-projects and each have their own build.gradle files; P1 and P2 also have build.gradle and settings.gradle files. How can I declare PP1 as a compile dependency in PP3's build.gradle file? apply plugin: 'java' dependencies { compile('P1:PP1') //does not work compile group: 'P1', name:

Gradle: How to configure multiproject setup with side-by-side projects

帅比萌擦擦* 提交于 2019-11-28 09:09:59
We have an old project that is set up like this: . ├── customizationProject │ ├── ejb │ └── services ├── projectA │ ├── ejb │ └── shared ├── projectB │ └── ejb └── projectC ├── ejb └── services The idea is that the customizationProject is where the final assembly of the delivered application happends, there might in fact be multiple customizationProjects and they might include multiple configurations. That, however is not the problem I'm tyring to solve. I want to make the customizationProject the logical root project of the gradle projects. How do I configure the individual projects, so that

Gradle multiproject optional subproject's transitive dependency should be resolved to an existing subproject

六眼飞鱼酱① 提交于 2019-11-28 02:11:21
问题 suppose the following project. the master project is a multi-project, however every part of the larger project can be developed individually or mixed in: /master/build.gradle /m1/build.gradle /m2/build.gradle /m3/build.gradle suppose m3 uses m2 and m2 uses m1 ( m1 <- m2 <- m3 ) the presence of m2 is optional a multi-project with the following layout also reasonable /master/build.gradle /m1/build.gradle /m3/build.gradle but in this case m2 would be pulled in from the artifact repository which

Require Gradle project from another directory

天涯浪子 提交于 2019-11-27 17:40:55
I have a directory/project setup like this: C:\ _dev\ Projects\ Logger MyProject Logger is an Android library project using Gradle. MyProject is a standard Android project project that needs to make use of the Logger library. I am using Android Studio and have tried adding Logger to the external libraries. Whilst this works during development, I get messages about the class not being found when building. I'm completely new to Gradle, but have tried the following in my build.gradle within MyProject : buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build

Gradle nested multi-projects with project compile dependencies

半城伤御伤魂 提交于 2019-11-27 15:36:31
问题 I have an identical problem to this Gradle Multi-Module Project Setup but I have to use project compile dependencies to build and cannot use the library(jar) dependencies solution that was given as a solution in the above question. Root |__ P1 | |_ PP1 | |_ PP2 | |__ P2 |_PP3 |_PP4 PP1, PP2, PP3 and PP4 are sub-projects and each have their own build.gradle files; P1 and P2 also have build.gradle and settings.gradle files. How can I declare PP1 as a compile dependency in PP3's build.gradle

Gradle exclude a specific subproject from full build

南笙酒味 提交于 2019-11-27 13:01:42
问题 In our Gradle project, we want to add a new module for functional-tests that needs to be able to access dependencies from other subprojects but still not be run as part of the full project build. If I try this, it still gets built: def javaProjects() { return subprojects.findAll { it.name != 'functional-tests' } } configure(javaProjects()) { ... } project(':functional-tests') { .... } The result is the same even if I move the functional-tests build to a separate build.gradle file of its own.

Multiple settings gradle files for multiple projects building

纵饮孤独 提交于 2019-11-27 06:48:29
I have the following project structure -->Starnderd Location -->Project1 -->settings.gradle -->build.gradle -->Subproject11 -->build.gradle -->Subproject12 -->build.gradle -->Project2 -->settings.gradle -->build.gradle -->Subproject21 -->build.gradle -->Subproject22 -->build.gradle -->build.gradle -->settings.gradle Idea of above project structure is that we have multiple projects which contains subprojects, each project can have dependencies to other projects. Also subprojects inside the project can have dependencies to other subprojects within the same project. Projects will be specified in

Gradle: How to configure multiproject setup with side-by-side projects

邮差的信 提交于 2019-11-27 02:44:56
问题 We have an old project that is set up like this: . ├── customizationProject │ ├── ejb │ └── services ├── projectA │ ├── ejb │ └── shared ├── projectB │ └── ejb └── projectC ├── ejb └── services The idea is that the customizationProject is where the final assembly of the delivered application happends, there might in fact be multiple customizationProjects and they might include multiple configurations. That, however is not the problem I'm tyring to solve. I want to make the

Require Gradle project from another directory

断了今生、忘了曾经 提交于 2019-11-26 22:35:33
问题 I have a directory/project setup like this: C:\ _dev\ Projects\ Logger MyProject Logger is an Android library project using Gradle. MyProject is a standard Android project project that needs to make use of the Logger library. I am using Android Studio and have tried adding Logger to the external libraries. Whilst this works during development, I get messages about the class not being found when building. I'm completely new to Gradle, but have tried the following in my build.gradle within

Gradle multiproject gives “Could not find property 'sourceSets' on project” error

自古美人都是妖i 提交于 2019-11-26 21:46:08
问题 I had quite good gradle configuration, that built everything just fine. But one of the projects of my multi-project build derived from the rest of them so much, that I would gladly move it to another git repo and configure submodules to handle it. First, I moved Project and its resources to subfolder Libraries/MovedProject . After altering some lines in gradle configurations it worked fine. But then I decided to write a new build.gradle just for this project, and move all configurations there