The cleanIdea pattern notwithstanding, I opened the pull-request to start a conversation about enhancing the plugin to support VCS. I'd be happy to enhance it to auto-detect VCS etc. Let me know what you think would help, or if you think it is somehow a nonstarter.
In my experience the idea plugin has been a huge selling point for gradle adoption, and people have actually asked me to help them figure out why Git isn't working afterwards.. I know, they should be able to figure it out themselves, but c'est la vie.. IMO, anything to make it easier to use is positive. On Sat, Apr 5, 2014 at 12:02 PM, Russel Winder <rus...@winder.org.uk> wrote: > On Sat, 2014-04-05 at 08:55 +1100, Adam Murdoch wrote: > > On 5 Apr 2014, at 8:27 am, Kallin Nagelberg > > <kallin.nagelb...@gmail.com> wrote: > > > > > I opened a pull request to allow VCS to be configured for intellij > > Projects: https://github.com/gradle/gradle/pull/263 > > > > > > Motivation: My workflow involves running 'gradle cleanIdea idea' > > fairly often, and It's annoying to have to reconfigure Intellij to > > recognize that it's a Git project every time. > > > > > > The pull request is currently quite simple, and I'm open to ideas > > for improvements. Maybe auto-detect VCS, do some sort of validation > > that the supplied VCS is valid for Intellij etc. > > > > > > I know that this can be accomplished by using withXml, but feel that > > creates an ugly build file for what I imagine is a very common use > > case. > > > > > > Thoughts? > > The defaults you are using just do not work for me so I would not be > happy supporting the pull request, but then my opinion doesn't actually > count :-) > > However, I think things could be better than they are now. Everyone > having to know the IntelliJ IDEA XML DOM is a good argument for getting > this handled in the Gradle plugin. The problem is managing change in > IntelliJ IDEA in the plugin: will the plugin be release in synchrony > with IntelliJ IDEA rather than with Gradle? > > > > Why do you use 'cleanIdea' so often (or at all)? The 'idea' task takes > > care of merging the changes into your existing project and module > > files. You should be able to just run 'gradle idea' and have it all > > just work. > > > In the past I found the only way to get a proper project file was the > cleanIdea idea way of working and have also got into this workflow. I > cannot remember what the problem was but I found that the idea task did > not take care of all the problems. However without actual data and > example this is just potentially false memory. > > I am finding that I have to manually set the source and test source > directories. Which is unexpected and a teeny bit frustrating. > > There are similar project initialization issues with the Eclipse project > build but I don't know anyone who has the equivalent initialization to > have this handled. > > -- > Russel. > > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:russel.win...@ekiga.net > 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
