(Please consider that I am very new to Gradle, though have been using Java/Eclipse for many years)
We are just converting from CVS/Ant to SVN/Gradle.
With CVS/Ant, when a given project had many artifacts to produce, we just added extra targets to the build.xml file.
Looking at Gradle, I’m thinking the preferred method would be to decompose the project to subcomponents each with their own build.gradle file. Fine so far.
But when I create a sample multi-project it creates multiple top-level projects that result in name collisions.
For example, using the Gradle IDE plugin for Ecilpse, creating a sample multi-project results in the following file structure:
test 1/ build/ build.gradle my-lib/ product/ settings.gradle
with some HelloWorld stuff in the source directories.
In Eclipse, this appears as THREE projects: - test1 - my-lib - product
This is a big issue.
When I’m working on a project, I like to check out multiple copies as I’m usually working on multiple tasks within the same codebase. This behavior of Gradle (or the GradleIDE plugin) actively prevents me from doing so.
For example, if I try to create another project ‘test2’ using the same multi-project template within Eclipse, it fails because both have ‘my-lib’ and ‘product’ subprojects.
Does anyone know a better way to handle this in Eclipse?