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

Executing 'mvn site' does not produce tag documentation #733

Closed
kwwall opened this issue Aug 17, 2022 · 0 comments · Fixed by #756
Closed

Executing 'mvn site' does not produce tag documentation #733

kwwall opened this issue Aug 17, 2022 · 0 comments · Fixed by #756

Comments

@kwwall
Copy link
Contributor

kwwall commented Aug 17, 2022

Describe the bug
Using Java 8, execute the

$ mvn site

command and the view the local file 'target/site/index.html' in your browser to verify that the tag-related documentation is missing or not produced.

Specify what ESAPI version(s) you are experiencing this bug in
ESAPI 2.5.0.0, which currently is the latest version of ESAPI.

To Reproduce
List the steps to reproduce the behavior or (ideally) attach a small JUnit test to reproduce the problem. Please be specific.

  1. From the shell, execute 'mvn site', as described above.
  2. Open the local file 'target/site/index.html' in your browser.
  3. Click on the 'Project Reports' link.
  4. Verify that the ESAPI tag-related documentation is not correctly created by observing that the following sidebar entries are either non-existent or produce errors when clicked on.

Expected behavior
The 3 files:

  • target/site/tagreference.html
  • target/site/tlddoc/index.html
  • target/site/taglibvalidation.html

should be created and when viewed in a browser window, they should render without any errors.

Platform environment (please complete the following information):

  • OS: Linux Mint 20.x
  • Browser: Chrome, Firefox
  • JDK version used with ESAPI: 8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants