IDEA preserve in project many other useful information(code style for example). I think we should try use directory based project configuration store format. Simple do not add to VCS files gradle*.xml from .idea directory. Possibility to configure gradle SDK per project is useful, but without global SDK it's pain, as you say. The best pattern(in my opinion) is when we have one global setting, and can override it per project if we want. Hope this and cool auto-completion for gradle scripts will be done in issue which I post earlier
2011/3/14 Mike <[email protected]> > I feel your pain. I'm not sure I have a good answer for you, but... > > Have you tried letting Gradle generate the Idea project for you rather than > check it into source control? Everyone would still have to set the path > themselves, but then you wouldn't have to worry about accidentally checking > it in. > > We have a similar issue, but in our case, each of our projects must define > a potentially different Gradle version (based on the version when we > released our product). We created a separate Idea plugin that sets the > Gradle path for us on startup. Unfortunately, its kind of involved. The gist > is you listen for projects being opened and then call > GradleUtils.setGradleSDKDirectory() with the new path. This will set the new > Gradle path in Idea and also reset the Gradle plugin so it loads from the > new location. > > Mike > Automated Logic Research Team > > --- On *Sun, 3/13/11, Владимир Рудев <[email protected]>* wrote: > > > From: Владимир Рудев <[email protected]> > Subject: [gradle-dev] Re: IDEA UI plugin. Plugin settings place question. > To: [email protected] > Date: Sunday, March 13, 2011, 1:15 PM > > > I looked at sources of gradle-UI plugin and JetGroovy - moving settings to > IDE can't be done simple, need to modify both plugins. I hope > this<http://youtrack.jetbrains.net/issue/IDEA-53476>issue resolve discomfort > and make gradle-script coding support much better. > > 2011/3/12 Владимир Рудев > <[email protected]<http://mc/[email protected]> > > > > I start use gradle and because I use IntelliJ IDEA I download gradle plugin > for it(UI). When I start use plugin I noticed some discomfort - when > collaborate in project whose developers use different OS gradle install path > is different. Every developer must manually setup 'gradle install path' into > *project* settings. We must not commit this path because it os-specific > but because it stored in project settings .ipr files stay always modified. > Maybe parameter 'gradle install path' should be configured and stored in IDE > area, not project? If so, I can create and resolve an issue. > Sorry for my bad english. > > -- > С уважением, > Владимир Рудев > [email protected] <http://mc/[email protected]> > > > > > -- > С уважением, > Владимир Рудев > (With regards, Vladimir Rudev) > [email protected] <http://mc/[email protected]> > > > -- С уважением, Владимир Рудев (With regards, Vladimir Rudev) [email protected]
