Skip to content

Rely on conventions to configure source and encoding of aggregated Javadoc task #31210

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

Closed
wilkinsona opened this issue May 30, 2022 · 0 comments
Assignees
Labels
type: task A general task
Milestone

Comments

@wilkinsona
Copy link
Member

wilkinsona commented May 30, 2022

source is hardcoded as 1.8 and encoding as UTF-8:

options {
author = true
docTitle = "Spring Boot ${project.version} API"
encoding = "UTF-8"
memberLevel = "protected"
outputLevel = "quiet"
source = "1.8"
splitIndex = true
use = true
windowTitle = "Spring Boot ${project.version} API"
}

In order to avoid problems like this one, the configured conventions should be used instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

1 participant