jbsupdater should allow for the consumption of -pool records by OpenJDK.
Going forward, N-pool records will be used for OpenJDK repos (and their corresponding closed counterparts) only. (e.g. 11.0.1, 11.0.2, 11.0.3)
N-pool-oracle records should be consumed by pushes to Oracle JDK repos. (11.0.3-oracle and subsequent releases)
Some complexity will arise from the fact that http://closedjdk.us.oracle.com/jdk-updates/jdkXX-cpu/ repos for LTS trains change definition after the 2nd update release. So while for the first two updates (e.g. 11.0.1, 11.0.2) they should consume N-pool records, beyond that they should only consume N-pool-oracle records.
Going forward, N-pool records will be used for OpenJDK repos (and their corresponding closed counterparts) only. (e.g. 11.0.1, 11.0.2, 11.0.3)
N-pool-oracle records should be consumed by pushes to Oracle JDK repos. (11.0.3-oracle and subsequent releases)
Some complexity will arise from the fact that http://closedjdk.us.oracle.com/jdk-updates/jdkXX-cpu/ repos for LTS trains change definition after the 2nd update release. So while for the first two updates (e.g. 11.0.1, 11.0.2) they should consume N-pool records, beyond that they should only consume N-pool-oracle records.
- duplicates
-
SKARA-1163 jbsupdater -pool record consumption modifications
-
- Closed
-
- relates to
-
SKARA-1448 Support specialized suffix pool records for legacy releases
-
- Resolved
-