[GRADLE-2832] IDEA plugin isn't downloading sources when mavenLocal() is used Created: 10/Jul/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

I am trying to get downloading of sources to work with a multimodule project.
Using the following entry gives me the correct IDEA-Project, except sources and javadoc aren't being downloaded.
Any idea why this doesn't work?

Idea-Config

allprojects {
apply plugin: 'maven'
apply plugin: 'idea'

idea {
module {
downloadJavadoc = true
downloadSources = true
}
}
}

And my repo-config:

repositories {
mavenLocal()
mavenCentral()
mavenRepo url: "http://repo.springsource.org/libs-milestone"
mavenRepo url: "https://repository.apache.org/content/repositories/snapshots/"
mavenRepo url: "http://source.mysema.com/maven2/releases/"
mavenRepo url: "http://repo.maven.apache.org/maven2"
}

configurations {
all*.exclude module: 'commons-logging'
}

 Comments   
Comment by Gradle Forums [ 10/Jul/13 ]

So you don't get dependency sources in the IDE? Which exact steps are you taking?

Comment by Gradle Forums [ 10/Jul/13 ]

The steps are:
gradle build (just to make sure the project builds)
gradle idea
Then open idea and open existing project (I am NOT using the builtin Idea-Gradle-support).
I can only jump into sources of libs that already are i my local Maven-Repo. No additional sources are being downloaded.

Comment by Gradle Forums [ 10/Jul/13 ]

Usually this works fine. My best guess is that the problem is related to `mavenLocal()`. Why do you declare that repository?

Comment by Gradle Forums [ 10/Jul/13 ]

Dang, here we go.
After removing mavenLocal() half of the internet started flowing onto my disk
Now I got my sources.
I was just hoping to keep as many of my dependencies as possible in one place.
Looks like I will have to live with that. Could be worse.

Thanks for the help!

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:32:44 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.