We have our developers gen the Eclipse files. They will see it as a broken build initially, but the nice thing is Eclipse will allow the files to change on the files system and you just refresh your workspace when the generation is done. I imagine IDEA would just notice the changes. Checking them into version control I agree would probably not work well unless you had a continuous build that could generate them and check them in on each build. Not sure I would recommend that either but it would be interesting to try for a couple iterations.
Jas On Tue, Oct 19, 2010 at 9:44 AM, Ben Dotte <[email protected]> wrote: > I was curious, how do people handle updating Gradle dependencies in a team > environment? > > We initially tried generating Eclipse/IDEA projects and checking them into > git with the idea that anyone updating dependencies should regenerate those > so everyone's IDEs will see the change (although this would still require > each person to run Gradle to download the dependencies). At least in this > scenario there would be some obvious missing dependencies, but we have had > issues getting this working. > > The alternative is to make each dev build their own IDE project files each > time build.gradle changes. I'm not sure how people would realize the build > changed. I suppose things might not compile, or something more subtle might > happen with slightly wrong library versions. > > We could try notifying people of the change, but often different people are > working on different branches of code, and may not need to rebuild until > well after the change. > > Ideally there would be better integration with Eclipse/IDEA, but in the > mean time I haven't come across a great way to handle this. > > -- > Ben Dotte > Lead Developer > Widen Enterprises, Inc. > 608-443-5439 >
