Merged
Conversation
Member
|
I assume that the javadoc is still working after that? ;) |
Contributor
Author
|
yes it is prose.css is really needed later can be imported in the xsl process rather than on each projet. |
mbien
approved these changes
Dec 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
404 on apidoc were a bit long to sort out but prose.css is leading to lots of error for almost no gain as css can be reached by other means.
Need a localhost as the current bits.netbeans swallow more 404 than expected.
I did a removal on apichanges.xml to avoid putting prose.css.
image for stability are shown again.