Re: [jakartaee-spec-project-leads] How to download your SPEC API for Jak

["Kevin Sutter" <sutter@xxxxxxxxxx>]

HI Scott,
>  How
should the Platform TCK project obtain your SPEC API for Jakarta EE 10
before you release your final SPEC API for EE10?  

Each of the Specification
projects should already have the ability to stage their APIs into the designated
"staging" repository:
https://jakarta.oss.sonatype.org/content/repositories/staging/

At the Platform
level, we have been using this capability for building the preliminary
versions (ie. RC) of the Uber Platform and Web Profile API jars.  We
use the following mvn command to build against this "staging"
repository.  The build process will look in this "staging"
directory before it attempts to find the dependencies in Maven central.

> mvn -Pstaging install javadoc:javadoc

You can reference
the pom.xml files and our README for this capability in our API repo:  https://github.com/eclipse-ee4j/jakartaee-api

This mechanism
should work just fine for the Platform TCK as well.

---------------------------------------------------
Kevin Sutter 
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter

Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)



From:
       "Scott
Marlow" <smarlow@xxxxxxxxxx>
To:
       jakartaee-spec-project-leads@xxxxxxxxxxx
Date:
       09/29/2021
14:45
Subject:
       [EXTERNAL]
[jakartaee-spec-project-leads] How to download your SPEC API for Jakarta
EE 10 TCK building?
Sent
by:        "jakartaee-spec-project-leads"
<jakartaee-spec-project-leads-bounces@xxxxxxxxxxx>

---

Some EE 10 SPEC API projects
will build their own TCK and do not need to answer the following question. 
For others that depend on the Platform TCK to generate the TCK that you
will use to validate that an implementation of your SPEC API passes 
Some EE 10 SPEC API projects will build
their own TCK and do not need to answer the following question.  For
others that depend on the Platform TCK to generate the TCK that you will
use to validate that an implementation of your SPEC API passes all TCK
tests, please respond to the question below.
How should the Platform TCK project obtain
your SPEC API for Jakarta EE 10 before you release your final SPEC API
for EE10?  
The Platform TCK team needs to setup
a job to generate the signature map files for JDK11 and ensure that we
build Standalone TCKs using the SPEC API changes that you will be including
in your final SPEC API release.
When you are ready to release your SPEC
API final release for EE 10, we will need to know that your relevant Standalone
TCK (that you are testing with) was built with the correct SPEC API. 
I'm thinking that the Platform TCK CI should produce a report of the SPEC
APIs used to build TCKs so that you can refer to that report and find the
`sha256sum` for your SPEC API that should match the SPEC API that you release
as final.
Your feedback on the above and suggestions
are greatly appreciated!
Scott



_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads