Thanks. So, I guess our Platform PRs for the Release Review will
need to be populated from multiple sources. I think that's fine for
Jakarta EE 8, but I wonder if this API processing should just be moved
to the Spec repo. Easier to keep everything in sync down the road.
Thanks for the
explanation on the current state. --------------------------------------------------- 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
Shannon <bill.shannon@xxxxxxxxxx> To:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>, Kevin
Sutter <sutter@xxxxxxxxxx> Date:
01:29 PM Subject:
Re: [jakartaee-platform-dev] Creation of javaee-api.jar and javaee-web-api.jar
I moved the creation of these jar files
to the jakartaee-apirepo. I just recently created Jenkins
jobs to build and release them.
It combines the API jar files from the individual APIs, which is why that
project needs to be updated with the new versions of the component API
jar files mas part of the release process.
Kevin Sutter wrote on 7/18/19 9:33 AM: Hi, As part of the Jakarta EE 8 prep work, I'm wondering about the creation
of the javaee-api.jar and javaee-web-api.jar. I'm assuming these
were previously created by just combining the contents of the various Java
EE component features. But, I'm not clear on the process for Jakarta
EE 8. Can anybody from Oracle shed some light on this process and
what needs to be done for Jakarta EE 8? In the mean time, I have created this Issue for tracking: https://github.com/eclipse-ee4j/jakartaee-platform/issues/80 Thanks!