This is an automated email from the ASF dual-hosted git repository.

weizhou pushed a change to branch 4.20-sonar-jre17
in repository https://gitbox.apache.org/repos/asf/cloudstack.git


 discard 137b965a90e jdk17: fix two unit test failures 
plugins/user-authenticators/ldap
 discard b4364515f70 jdk17: replace gmaven-plugin in all pom.xml files
 discard 35981e744af jdk17: fix brocade-vcs
 discard 6b0f73525e8 jdk17: fix unit tests in engine/storage/datamotion
 discard 2d1d401e68e engine/service/pom.xml: fix maven-war-plugin version
 discard cc0b4e41e39 pom.xml: add-exports
 discard 7a2020c05e8 jdk17: replace MaxPermSize by MaxMetaspaceSize
 discard 4c5b5a5dba8 engine/schema/pom.xml: replace gmaven with gmavenplus
 discard 828c429ebcc pom.xml: fix error 'module java.base does not "opens 
java.lang" to unnamed module'
 discard 1222eef0165 Merge remote-tracking branch 'apache/main' into 
4.20-sonar-jre17
 discard b16d00adee4 .github: use JRE17 for sonar check
     add e520525fe73 Use parameter dcId as wrapper to prevent NPE (#8986)
     add b91c3879c81 ui: add support to change Account role for admins (#9012)
     add ea11128cb37 linstor: disconnect-disk also search for resource name in 
Linstor (#9035)
     add 92ba4765930 Merge release branch 4.18 to 4.19
     add 0d8f7d40037 Merge release branch 4.19 to main
     add 2f85f20c799 .github: use JRE17 for sonar check
     add 2a73cc1d0d0 pom.xml: fix error 'module java.base does not "opens 
java.lang" to unnamed module'
     add 6642079a9ca engine/schema/pom.xml: replace gmaven with gmavenplus
     add 3ed62ca5990 jdk17: replace MaxPermSize by MaxMetaspaceSize
     add ef61eb1788d pom.xml: add-exports
     add 2f9a718ba21 engine/service/pom.xml: fix maven-war-plugin version
     add 1ec27fcc924 jdk17: fix unit tests in engine/storage/datamotion
     add dfed7995193 jdk17: fix brocade-vcs
     add 08e7019157f jdk17: replace gmaven-plugin in all pom.xml files
     add 4d93b134df7 jdk17: fix two unit test failures 
plugins/user-authenticators/ldap

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (137b965a90e)
            \
             N -- N -- N   refs/heads/4.20-sonar-jre17 (4d93b134df7)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 .../cloudstack/engine/subsystem/api/storage/EndPointSelector.java  | 2 +-
 .../cloudstack/storage/endpoint/DefaultEndPointSelector.java       | 3 ++-
 .../com/cloud/hypervisor/kvm/storage/LinstorStorageAdaptor.java    | 7 ++++---
 ui/public/locales/en.json                                          | 1 +
 ui/src/config/section/account.js                                   | 2 +-
 5 files changed, 9 insertions(+), 6 deletions(-)

Reply via email to