Open JontomXire opened 6 months ago
Also, at the start of the build I get:
> Configure project :
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
After removing the two lines that caused errors, I get:
`> Task :fmlearlydisplay:javadoc FAILED /home/alastair/Development/MinecraftForge/fmlearlydisplay/src/main/java/net/minecraftforge/fml/earlydisplay/DisplayWindow.java:343: error: invalid use of @return
FAILURE: Build failed with an exception.
Javadoc generation failed. Generated Javadoc options file (useful for troubleshooting): '/home/alastair/Development/MinecraftForge/fmlearlydisplay/build/tmp/javadoc/javadoc.options'`
I assume that people do actually use JavaDoc when creating mods, rather than some sort of psychic power that I lack, and as such that they manage to actually generate the javadocs? But this is getting silly!
Most people do not use stand alone javadoc, they use their IDE to navigate around the source and read the docs it displays.
So ya, some of the javadocs in the project may not pass the javadoc parser's strict requirements.
You could try adding the -Xdoclint:none
argument to lessen the strictness.
If you wanna do a PR that fixes the javadoc issues, feel free. But as I said, most people don't care these days.
What is the syntax to specify "-Xdoclint:non"? Where do I add this?
I tried:
$ ./gradlew -Xdoclint:none javadoc
Unknown command-line option '-X'.
Many of the bugs are documentation errors. Whether the documentation refers to a parameter that does not exist or has had a name change, or the documentation refers to a class or somesuch that no longer exists.
I am fixing things as best as I can, but in the case of some "reference not found" errors I am simply deleting the relevant sentence.
Do I have to clone to do a push request? I created a branch from 1.20.x but cannot push it or the changes on it.
I would prefer not to clone just to create a merge request so I am attaching the diffs here. MinecraftForge_diffs.txt
Also, the generated javadoc does not include any of the underlying Minecraft stuff, which is the stuff I am really after! How do I generate javadocs like these: https://nekoyue.github.io/ForgeJavaDocs-NG/javadoc/1.19.3/
Minecraft Version: 1.20.x
Forge Version: Branch 1.20.x, commit ed2ba0f
Logs:
Steps to Reproduce:
If these are not the correct steps to generate the javadocs, then what are? I cannot find any up to date information on generating javadocs on the command line (Linux).
Description of issue:
Javadocs are not generated.
This was also reported in December 2022 on the forums at https://forums.minecraftforge.net/topic/118731-is-there-a-forge-api-or-javadoc/ where the OP states "I have unsuccessfully tried to create the Javadoc from the MinecraftForge Github repository.".
This issue may be resolved by adding documentation on the steps required to generate the JavaDocs, of which there currently appears to be none.