On Dec 26, 2008, at 10:58 PM, Adam Murdoch wrote:
Hans Dockter wrote:
It is quite a pain to create the new module file for a Gradle
IntelliJ project as the dependencies are no longer in a lib folder
but come from the local cache.
I have added an 'ide' task to the Gradle build, which will copy all
the runtime and test runtime jars into the 'lib' directory (ie where
they used to be). Then you can just point IntelliJ at the lib
directory rather than into various spots in the cache. Plus when the
dependencies change, you can just re-run the task and IntelliJ will
pick up the changes. At some point I'd like to extend this to fetch
the source artifacts as well.
This is nice.
Personally, I would like something like the 'ide' task in one of the
plugins, as something I could use along with, or instead of, the IDE
project generation tasks. Perhaps we need an 'ide' plugin with all
this kind of stuff in it.
I see the following advantages of the 'copy to project lib' approach:
- It works also with repositories that are not cached (e.g.
FlatDirResolver)
- It does not interfere with your other IDE settings if you do
something fancy there.
And as you said, It would be really cool when doing the IDE project/
module generation, to have a choice between cache and 'copy to project
lib'.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
