Skip to content

Fix Publish-Javadoc Action#968

Open
busabj wants to merge 13 commits intoBram-Hub:devfrom
busabj:master
Open

Fix Publish-Javadoc Action#968
busabj wants to merge 13 commits intoBram-Hub:devfrom
busabj:master

Conversation

@busabj
Copy link
Copy Markdown
Collaborator

@busabj busabj commented Mar 24, 2026

Description

Under Actions --> Publish Javadoc, the workflows were unable to be published since there were errors. This was an important problem because the previously published Javadocs shown on the ReadMe were very outdated. Changes were made to the publish-javadoc.yml and the build.gradle files in order to build the Javadoc correctly with the correct version, without any errors.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Enhancement (improvement to an already existing feature)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

In my fork, I went to Actions --> Publish Javadoc, and was able to successfully publish it. I then went to Settings --> Pages --> Visit Site, and was able to see the correct Javadoc. I then went through the site and made sure descriptions were correct.

Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

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

Successfully merging this pull request may close these issues.

2 participants