The second PR is giving the actual content that is going into the website for the spec, so its a transformation of the api jar that I don’t know can be without a good deal of effort on the website side.
Hi,As I continue
to review these PRs, I'm questioning the use of the second apidocs PR.
How do we plan to process the javadoc that we're pushing to this
repository?I'm finding it's
easier to review the content of jakarta.<spec>-<version>-javadoc.jar
file than to review the content on the PR.The combined "jakarta
ee api" jar file is created by accessing the maven artifacts and re-generating
all of the javadoc.So, I'm just wondering
what we're accomplishing with the extra PR. Maybe we should just
have a pointer to the staging repo for the javadoc jar file? Again,
if we're too late to change the process, then I'm fine with that. Or,
maybe I need some education as to what the separate PR buys us. Or,
maybe I'm working too late this evening... :-) Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
|
