specfically:

apply plugin: idea

then from gradle:

gradle idea


All your project/module files will be generated for you.

On Fri, May 20, 2011 at 6:33 PM, Roger Studner <[email protected]> wrote:
> Was curious how most of the people here, who work/use gradle.. also use
> their IDE of choice.
>
> In my case.. i've relied on doing tasks like this:
>
> subprojects {
>
> ..
> stuff
> ..
>    task gatherSubProjectDependencies(dependsOn:
> configurations.runtime.buildArtifacts, type: Copy) {
>      into('libs')
>      from configurations.runtime
>      from configurations.runtime.allArtifacts*.file
>    }
>
> }
>
>
> task gatherProjectDependencies(type: Copy) {
>   subprojects {
>       dependsOn project.configurations.runtime.buildArtifacts
>       from project.configurations.runtime
>       from project.configurations.runtime.allArtifacts*.file
>   }
>   into('libs')
> }
>
> I got the jist of these form this mailing list.. but in essence..
> gatherProjectDependencies, run from the ROOT of a multi project build..
> gathers all jars, from all subprojects.. info one folder
>
> gatherSubProjectDependencies does about the same.. but does it just the same
> at only each subproject level.
>
> So, two points/things:
>
> 1) I am not 100% sure why they work (haha)
>
> 2) Is this the same technique most gradle experts/day to day people are
> using?
>
> Just curious, on a BIG project, how you resolve/get all your jars.. so the
> STS or INtellij can let you work on the code
>
> I'm sure the answer to my question would be useful for a whole slew of
> people on the 'edge' of adopting gradle full time
>
> Best,
> Roger
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to