On Dec 27, 2008, at 12:32 AM, Tom Eyckmans wrote:
I like the idea of an ide plugin very much. We could do something
similar with ide as with testframeworks ( renamed from
testconvention to testframework to prevent confusion ):
like in test:
test {
useJunit() / useTestNG() / ...
}
ide {
useIntelliJ() / useEclipse() / ...
retrieveSources ( default for all dependency configurations ?
transitive yes/no? )
}
just a thougth
I think it makes a lot of sense to have an common abstraction on top
of IntelliJ/Eclipse/NetBeans for IDE stuff. Steven Devijver had
another idea on top of this which I really like. Plugins should be
able to communicate which each other. In the case of our future IDE
plugin this means. A plugin which is not written by us marks itself as
IDEAware. In this case, the IDE plugin passes an IDEConf object to
this external plugin and the external plugin can read/modify the
IDEConf.
- Hans
2008/12/26 Adam Murdoch <[email protected]>
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.
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.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
