JAVA-22625: Changes made for module Q to S formatting the pom.xml (#14330)

This commit is contained in:
Bipin kumar
2023-06-30 16:37:55 +05:30
committed by GitHub
parent 4a2c365472
commit c6a6279724
23 changed files with 45 additions and 43 deletions
+1 -1
View File
@@ -20,7 +20,7 @@
<module>spring-security-cognito</module>
<module>spring-security-core</module>
<module>spring-security-core-2</module>
<!-- <module>spring-security-ldap</module>-->
<!-- <module>spring-security-ldap</module>-->
<module>spring-security-legacy-oidc</module>
<module>spring-security-oauth2</module>
<module>spring-security-oauth2-sso</module>
@@ -1,5 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -1,5 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
@@ -1,5 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -129,7 +129,6 @@
</plugins>
</build>
<!-- NPM build is disabled from profile specific configurations because in a multi-threaded run environment -->
<!-- like Jenkins this build was not succeeding due to issues totally unrelated to this module This -->
<!-- can be enabled manually while running this module on local, or directly npm can be run inside -->