Just realized that Eclipse will put absolute paths in .classpath for jars and javadoc jars. Guess I need to change my project setup and not have .classpath in version control. Makes sense.

That said, it would still be nice if Gradle could handle an existing project's jar:resource: Javadoc locations. Or am I missing something else?

Can you tell us what Eclipse version you use and how did you create that classpath entry definition? I guess there are some ways how to fix this in Gradle: probably we need to add URL handler for 'platform:' protocol or parse this as simple String.

In the meantime: my first choice would be to use a repository like Artifactory or Nexus for your binary dependencies rather than adding them to your project (and possibly to SCM). This will take care of the association with sources and javadoc in most cases too.

This is Eclipse Kepler, Build id: 20130614-0229.

To add a javadoc jar, go to Java build path settings, then the Libraries tab. Open any library, click the Javadoc location, then click Edit... Select Javadoc in archive, select Workspace file, select the docjar in Archive path.

I agree that jars should not be in the SCM. This is an ant-based project and I want to get it working with Gradle without breaking ant. I'll have a hard time selling gradle in the company if it breaks the current build.

Although we do not support generating jar:platform:/resources/path/../file-javadoc.jar!/ we should be able to read a classpath file with this content and preserve it. A problem here is that our FileReference is not flexible enough and also our model in ToolingAPI only uses Files. To fix it we would need to extend these places to read those values and export them again.

Optionally we can try to use this kind of URI for all javadoc files inside workspace as this would make .classpath file more portable.

FYI, this also fails for maven packages which do not provide javadoc jars when you try to add a web-URL as javadoc setting, either manually or via something like discussed at http://stackoverflow.com/questions/18518020/gradle-how-to-specify-javadoc-location-jar-file-for-maven-dependency

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!

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.