Skip to content
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

Run a test build of the platform api/javadoc using Java 11 to see what issues might exist. #110

Closed
starksm64 opened this issue Aug 31, 2021 · 5 comments

Comments

@starksm64
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We know there are problems with moving from Java 8 to Java 11 javadoc generation, so we need to know what the scope of the problem is.

Describe the solution you'd like
Many spec project that have updated to Java 11 have seen errors. They either had to disable certain features or fix the javadoc source.

Describe alternatives you've considered
None.

Additional context
It was noted on the Aug 31 2021 platform call that we should start looking at this to see what the scope of the problem might be.

@kwsutter kwsutter transferred this issue from jakartaee/platform Sep 2, 2021
@kwsutter
Copy link
Contributor

kwsutter commented Sep 2, 2021

I'm going to transfer this Issue to the jakartaee-api repository since that's where we track the Platform API and Javadoc from.

@kwsutter
Copy link
Contributor

kwsutter commented Sep 2, 2021

This Issue is related to Issue #107. Some of the work was completed via PR #109. The Jenkins build was already updated to build with Java 11. More scrubbing of the warnings produced is still probably warranted. But, I think it's in pretty good shape.

@kwsutter
Copy link
Contributor

kwsutter commented Sep 9, 2021

Triaging the warnings that are generated from the javadoc generation. Here are the Issues or PRs that I created or added a comment to...

And, that's about it. Otherwise, the generation of the api and javadoc looks clean for Java 11.

@kwsutter
Copy link
Contributor

kwsutter commented Sep 9, 2021

There are also these warnings, but these should be expected since we are not defining modules at the uber jar level for Jakarta EE 10:

[INFO] --- maven-javadoc-plugin:3.1.0:javadoc (default-cli) @ jakarta.jakartaee-web-api ---
[WARNING] Unable to derive module descriptor for /Users/[email protected]/git/jakartaee-api/jakartaee-web-api/target/jakarta.jakartaee-web-api-10-SNAPSHOT.jar
[INFO] --- maven-javadoc-plugin:3.1.0:javadoc (default-cli) @ jakarta.jakartaee-api ---
[WARNING] Unable to derive module descriptor for /Users/[email protected]/git/jakartaee-api/jakartaee-api/target/jakarta.jakartaee-api-10-SNAPSHOT.jar

@lukasj
Copy link
Contributor

lukasj commented Sep 9, 2021

mail is supposed to be fixed already in 2.1.0-RC1 (available in central)

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

No branches or pull requests

3 participants