Eclipse OpenJ9: A Java Virtual Machine for OpenJDK that's optimized for small footprint, fast start-up, and high throughput. Builds on Eclipse OMR (https://github.com/eclipse/omr) and combines with the Extensions for OpenJDK for OpenJ9 repo.
Other
3.28k
stars
720
forks
source link
Profiles name without version part but have same beginnings of the profile name will be treated as one profile but different versions #20518
When try to load one profile, for example the “RestrictedSecurity.Test-Profile-PolicySunset” profile in method “private static void getProfileID(Properties props)”. It will go into the “without version part” codes. And in that part of codes, we used the “key.startsWith(potentialProfileID)”, the “startsWith” check. So, the profile “RestrictedSecurity.Test-Profile-PolicySunset” and “RestrictedSecurity.Test-Profile-PolicySunsetFormat” will be treated as one profile but different versions. And due to both of them set as default profile, then the multiple default error will happen.
If there are two profiles, example below, without the version but all are the base profile, and all as default profile.
When try to load one profile, for example the “
RestrictedSecurity.Test-Profile-PolicySunset
” profile in method “private static void getProfileID(Properties props)
”. It will go into the “without version part
” codes. And in that part of codes, we used the “key.startsWith(potentialProfileID)
”, the “startsWith
” check. So, the profile “RestrictedSecurity.Test-Profile-PolicySunset
” and “RestrictedSecurity.Test-Profile-PolicySunsetFormat
” will be treated as one profile but different versions. And due to both of them set as default profile, then the multiple default error will happen.