Nice - that solves my problem. Since the war plugin already has a providedCompile configuration couldn't the idea plugin pick up on this automatically? This way it could work out correctly out-of-the-box.
Regards, Glen On 10 August 2011 16:58, Szczepan Faber <[email protected]> wrote: > That's exactly right. It is documented here: > http://gradle.org/current/docs/dsl/org.gradle.plugins.ide.idea.GenerateIdeaModule.html > > Cheers! > > > On Wed, Aug 10, 2011 at 4:22 AM, Hani Suleiman <[email protected]> wrote: > >> I think this is the magic you need: >> >> apply plugin: 'idea' >> >> configurations { >> provided >> } >> >> idea.module { >> scopes.PROVIDED.plus += configurations.provided >> } >> >> >> Then you can declare any dependency as 'provided' and it'll create the >> right scope for the .iml files, for example: >> >> dependencies { >> provided 'javax.servlet.jsp:jsp-api:2.1' >> } >> >> On Aug 9, 2011, at 10:10 PM, Glen Stampoultzis wrote: >> >> > Hi, >> > >> > I use Gradle to generate my idea project files. For the most part this >> works well but I have a small issue with scopes. It seems that Gradle only >> supports Idea compile and runtime scopes. When I create my artifacts I find >> that my providedCompile dependencies are put into the compile scope and I >> have to go manually change this each time. Is this just an unsupported >> feature of the Idea plugin or a bug? >> > >> > Ideally it would be nice to have the idea plugin also generate the >> artifacts as well but maintaining those manually is not too hard. >> > >> > - Glen >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > -- > Szczepan Faber > Principal engineer@gradleware > Lead@mockito >
