I haven't looked at the code, but I imagine it's doing the same thing that maven doing in this realm. It takes all your dependencies and adds the sources and javadoc classifier to them internally then tries to find those jars. You shouldn't have to do anything to your build to get them to show up when you let Gradle create the IDEA / eclipse project. You'll have to have those jars in the local repo though. I also have not tried this pointing to an Ivy repo, only maven, so rules may be different.
On Tue, Aug 17, 2010 at 18:38, Benjamin Jansen <[email protected]> wrote: > Hello, > > I am trying to understand how the gradle idea plugin expects to find source > artifacts for dependencies, but I have not found any documentation describing > it and my groovy-fu is not up to snuff to understand what exactly happens in > IdeaModule.groovy. I'm using a local ivy repository for my dependencies. > Based on what I could grok from IdeaModule.groovy, I added an artifact > "<primary artifact name>-sources.jar" to one of my dependencies but > gradle-idea just added it as another regular dependency on the idea module. > > Is there a document describing how source & javadoc artifacts should be > configured/named so that the gradle idea plugin finds them? > > Thanks, > Ben Jansen > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
