> I'm surprised the gradle team doesn't get hugely annoyed every time this file > is generated and you lose all the above!
Have you used it? It doesn't remove all the above :) It keeps all that stuff if you run 'gradle idea'. Both eclipse & idea plugins merge the content of your existing IDE descriptors with information from gradle. Cheers! On Tue, Jul 19, 2011 at 1:14 PM, Hani Suleiman <[email protected]> wrote: > On Jul 18, 2011, at 10:20 PM, Peter Niederwieser wrote: > >> >> Hani Suleiman wrote: >>> >>> Some questions about this as I'd dearly love to use it but have a few >>> concerns... >>> >>> - Why is it generated the old .ipr format, rather than files using the >>> .idea directory format?' >>> >> >> This is the first time I hear that .ipr is the "old" format. Isn't it still >> the default in IDEA? How is the "new" format better except that it allows to >> check in some parts but not others in to source control? >> > That's a pretty big win. It also is a lot more sensible in terms of what it > contains. Things like run configurations, inspection profiles, and so on. It > also means that you can have more fine grained control over what you generate > and overwrite. It also means that we can check in files that gradle does not > generate (run configurations, for example) and not lose them every time we > add a dependency. > > If you think about it, it makes absolutely no sense to have to redo all your > run configs, project style customization, compiler settings, inspection > settings, and others just because you now need a new version of groovy or > whatever. It's problematic enough to make the current idea module unusable as > more than a one-off to generate stuff from scratch. > >> >> Hani Suleiman wrote: >>> >>> - The workspace file is supposed to be a user's private workspace settings >>> (open editors, etc), what's the point of ever generating this? >>> >> >> I'm not sure if you can open a project without an .iws, but maybe we can do >> better here. Any suggestions? In the Gradle build itself we use this for >> sharing run configurations across the team (integration tests, run Gradle, >> etc.). > > If you switched to the directory format, you get all that without having to > pollute 'personal' settings like which files you have open. > > You can definitely open a project without an .iws, .iws is the 'workspace' > file which contains some pretty important things that you rarely want shared, > but also never want clobbered by a tool: > > - Breakpoints you've set > - Open editors > - Local changesets (redundant with git, but still) > - Last opened files > - Pinned/docked window settings > - Local run configs (run/debug configs you want locally without sharing with > everyone else) > > I'm surprised the gradle team doesn't get hugely annoyed every time this file > is generated and you lose all the above! > > Given that you guys seem to be using IDEA, how do you cope with all the > above? Don't these pain points affect you? > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
