All of the apidocs links for netlify preview do not work.
For example, Jakarta Persistence, in the page "https://deploy-preview-714--jakartaee-specifications.netlify.app/specifications/persistence/3.2/" the link of apidoc is "https://deploy-preview-714--jakartaee-specifications.netlify.app/specifications/persistence/3.2/apidocs".
When I click this link, I am redirectec to "https://deploy-preview-714--jakartaee-specifications.netlify.app/specifications/persistence/3.2/jakarta.persistence/module-summary.html". But this page is not found.
The correct page is "https://deploy-preview-714--jakartaee-specifications.netlify.app/specifications/persistence/3.2/apidocs/jakarta.persistence/module-summary.html".
Note that the links work correctly on the Jakarta EE website when merged.
(How one can reproduce the issue - this is very important)
See description above
(What actually happens)
(What you should see instead)
(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")
Hi,
Please check why James is not showing up as a committer for Jakarta RESTful Web Services after election completed successfully election:
The same goes for Maximillian for Jakarta Data:
Note: I noticed some sort of error red warning message when I approved the elections as the PMC. I think the text said something about ECA and that Webdev would address the issue.
Ivar
James now shows up, so we can close this issue.
Looks like it worked this time. Let's see if he shows up on the PMI page and as a committer on GitHub before closing the issue
That's weird. I have approved it. Actually, I did it at the same time as I approved Maximilian's. I even saw that it had the +1 on the page. That was when I got the warning message. I'll do it again and hope it goes better this time.
Hi,
Please check why James is not showing up as a committer for Jakarta RESTful Web Services after election completed successfully election:
The same goes for Maximillian for Jakarta Data:
Note: I noticed some sort of error red warning message when I approved the elections as the PMC. I think the text said something about ECA and that Webdev would address the issue.
Ivar
Yes, I got an error message when I approved the election result (as PMC).
Yes, the milestone releases of the individual specifications are due November 28, so it makes sense to be able to help out the potential stragglers to pass the finishing line.
We are talking about the projects producing specifications listed under https://jakarta.ee/specifications/.
The release coordinators would need to be able to configure and run builds.
For every major Jakarta EE release, the Jakarta EE Platform Project selects a release coordinator with the task of coordinating the releases of all the Jakarta Specifications that are a part of the release. The release coordinator may differ from release to release.
It would be helpful if the release coordinator could get access to the Jenkins CI for all the Jakarta Specification Projects without being a committer on all those projects.
What we would like to have:
Thanks for fixing it so swiftly
(Summarize the bug encountered concisely)
Link on the page (example from MVC, but applies to all specifications: https://jakarta.ee/specifications/mvc/2.1/apidocs
When clicking on the link, the following is redirected to: https://jakarta.ee/specifications/mvc/2.1/jakarta.mvc/module-summary.html
NOTE the apidocs
element is missing from the URL
The source for the link in the _index.md file is:
* [Jakarta MVC 2.1 Javadoc](./apidocs)
https://raw.githubusercontent.com/jakartaee/specifications/master/mvc/2.1/_index.md
Don't know if this is a "feature" of Hugo, or the generation script
https://jakarta.ee/specifications/mvc/2.1/apidocs/jakarta.mvc/module-summary.html
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")
Developers can not access the documentation.
I had the same problem when I connected with my existing personal Microsoft account. So I created a new one with my Eclipse email. If webmaster has an existing account, it may be needed to create a new one?
The project is ongoing and Ed (as the release coordinator) needs it as soon as possible.
Can we bump the priority for this one? The Jakarta EE Platform project needs this for managing the release of Jakarta EE 11.
+1
Let's just close this issue. I'll open a new more specific one if needed.