New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle should pass empty -sourcepath to javadoc (like it does for javac) #5630
Comments
This work-around does not work with: |
Just tested, and yes it does: you need to apply the workaround to all Javadoc tasks in all projects and subprojects (the |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request. |
Expected Behavior
Javadoc shouldn't fail (or even warn) on source files that are not in the project (i.e. in third-party dependencies)
Current Behavior
Javadoc warns, and in some times even fails (I believe in this case it's a bug in javadoc, but still), about source files that are actually packaged in third-party dependencies (i.e. present in the classpath); specifically here
com.google.gwt:gwt-user:2.8.2
.Context
GWT libraries bundle their source files, these interfere with javadoc, the way it's currently configured.
This is actually similar to #414.
A workaround is to
addStringOption("sourcepath", "")
in the javadoc task.Steps to Reproduce (for bugs)
It happened to me at some point when working on https://github.com/gwtproject/gwt-events; but it can be reproduced at gwtproject/gwt-event@b2b3704f.
Your Environment
The text was updated successfully, but these errors were encountered: