Yes, it's that easy. If IJ is running, it detects the changed files and will prompt you to reload/reinitialize
On Sat, May 21, 2011 at 10:26 AM, Roger Studner <[email protected]> wrote: > As a project (multi-module... with new modules having very new > dependencies etc) grows over time.. and you *fully recreate* the project > files.. is it simply a matter of restarting intellij? > > I mean.. I want to believe it is that easy right :)? > > I guess it is the multi-module/hierarchy stuff that starts to worry me over > time. > > i've seen frlom m2eclipse and IvyDE that 'magical instant resolving' is > actually bad at times.. > > I personally don't mine a very manual approach... i've made gradle build > files for a *large* project at work and am trying to simply sell switching > over to gradle > > So i'm basically just doing my homework from the great minds of the mailing > list ;) > > Roger > > > ------------------------------ > > phil swenson <[email protected]> > May 21, 2011 9:27 AM > > specfically: > > apply plugin: idea > > then from gradle: > > gradle idea > > > All your project/module files will be generated for you. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > ------------------------------ > > Roger Studner <[email protected]> > May 20, 2011 8:33 PM > > 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 > > >
<<postbox-contact.jpg>>
<<compose-unknown-contact.jpg>>
