Hello,
I recently started to work at a company which has an ant based build
process. Since it has some drawbacks, I was looking for a better build
management tool, so I came to gradle. I already (unfortunately) have a list
of questions, so let's get started with the first:
We have the following structure of repositories and eclipse projects:
Repository A ("common")
- Project A1
- Project A2 (depends on A1)
- Project A3 (depends on A1 and A2)
Repository B (second "common")
- Project B1 (dep: A1, A2)
- Project B2 (dep: A1, A2, B1)
Repository C (product)
- Project C1 (dep: A1, A2)
- Project C2 (dep: A1, A2, C1, B1, B2)
- ...
Repository D (another product)
- Project D1 (dep: A1, A2)
- Project D2 (dep: A1, A2, D1)
- ...
Repository ...
- ...
This tree is reflected within the file system and by the version control
system. The parent directory of the repositories is /not/ under version
control.
I first assumed that I would need one settings.gradle and build.gradle per
repository directory, and optionally I would place one in the project
directory (for project-specific instructions).
But then how do I refer from the product repositories to the common
repositories?
Or do I place a settings.gradle only in the product repositories? This seems
wrong to me, because
1) I don't want to repeat the dependency information within the common
repositories in the settings.gradle of the products (e.g. A2 depends on A1)
and
2) I would like to be able to build any common repository separately
Or:
The builds within each project produce JAR artifacts. Does it mean that I
need to specify the product dependencies on the common repos via the output
artifacts?
I hope the description of the problem is fairly clear.
Thanks in advance for infos,
Björn
--
View this message in context:
http://gradle.1045684.n5.nabble.com/How-to-set-up-multi-product-builds-tp4716825p4716825.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
