Newbie needs advices and best practises to move to Gradle

Hi, first message here, please be kind :smiley:

I’m totally aware I’m coming here with pretty general questions, but your answers would certainly help me a lot. I’m investigating into Gradle and Wuff to migrate our proprietary build system to Gradle. We develop some products made of Eclipse plugins, features and RCP components. But we can NOT use a single couple Java/Eclipse to build those products. Indeed, one project could be built with Java 6 / Eclipse 3.6 while another with Java 7 / Eclipse 4.4. There is not a single rule. So having such a flexibility with our build system is a must, and we have about 100 projects in the company. The “real” build part is done with Eclipse PDE.

Currently, our build system (made of a dedicated computer + a bunch of Powershell scripts + a home made web interface) runs the following sequence:

  • Read our projects list (a locally managed file) to get the project URL (Powershell)
  • Clone the project from our GIT server (Powershell + BitBucket)
  • Read the project build configuration (Powershell)
  • Gather all dependencies to assemble a whole Eclipse environment (Powershell)
  • Within this newly created Eclipse, run PDE to build the project (Eclipse PDE)

I’ve the feeling (that’s why I’m posting, hoping some answers and help) Wuff will only replace the last part (PDE run), but for all the stuff involved before the project is cloned locally, I’ll still have to deal with specific parts (written with Gradle of other scriping language).

I will greatly appreciate people with similar large build systems share their thoughts and feedback about how to use Gradle the best way, even if each situation is, of course, specific.


N.B.: I’ve already read pretty much all the Gradle doc.

You might be interested in how the buildship eclipse plugin is built and also this discussion

1 Like

That’s definitely some help, thanks a lot @Lance_Java!