Javadocs broken - again
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 752
- Forks
- 307
- Avg merge
- 15h 48m
- Merged PRs (30d)
- 7
Description
I have no idea if anybody cares to spend time on this, I've already wasted enough hours on this that my only solution at this point would be to migrate away from maven for handing this mess as the tooling there seems a bit nicer, but, I'm not sure that I can justify the effort that would go into such a thing, or if it's worth fighting the maven side of stuff again
ref, missing submodules, i.e. chat
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Maven build configuration and reproducing the broken Javadocs generation. Check the missing submodules referenced in the issue, including chat, and determine the specific build failure before proposing a fix. Done means Javadocs generate successfully with the required submodules present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100