iSharkFly-Docs/java-tutorials
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

JAVA-7178: Fix formatting of POMs (#11236)

Browse Source 
* JAVA-7178: Fix formatting of POMs

* JAVA-7178: fix failing build
This commit is contained in:
freelansam
2021-09-20 00:04:26 +05:30
committed by GitHub
parent ae17173f90
commit fe7d2af8c0
91 changed files with 461 additions and 548 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spring-security-modules/pom.xml
+1 -1
View File
@@ -49,4 +49,4 @@
<module>spring-social-login</module>
</modules>
</project>
</project>
spring-security-modules/spring-security-web-react/pom.xml
+22 -90
View File
@@ -108,41 +108,17 @@
</warSourceExcludes>
</configuration>
</plugin>
<!-- 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 the webapp folder
-->
<!-- <plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<version>${frontend-maven-plugin.version}</version>
<configuration>
<nodeVersion>${node.version}</nodeVersion>
<workingDirectory>src/main/webapp/WEB-INF/view/react</workingDirectory>
</configuration>
<executions>
<execution>
<id>install node and npm</id>
<goals>
<goal>install-node-and-npm</goal>
</goals>
</execution>
<execution>
<id>npm install</id>
<goals>
<goal>npm</goal>
</goals>
</execution>
<execution>
<id>npm run build</id>
<goals>
<goal>npm</goal>
</goals>
<configuration>
<arguments>run build</arguments>
</configuration>
</execution>
</executions>
</plugin> -->
<!-- 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 the
webapp folder -->
<!-- <plugin> <groupId>com.github.eirslett</groupId> <artifactId>frontend-maven-plugin</artifactId>
<version>${frontend-maven-plugin.version}</version> <configuration> <nodeVersion>${node.version}</nodeVersion>
<workingDirectory>src/main/webapp/WEB-INF/view/react</workingDirectory> </configuration> <executions>
<execution> <id>install node and npm</id> <goals> <goal>install-node-and-npm</goal> </goals> </execution>
<execution> <id>npm install</id> <goals> <goal>npm</goal> </goals> </execution> <execution> <id>npm run
build</id> <goals> <goal>npm</goal> </goals> <configuration> <arguments>run build</arguments> </configuration>
</execution> </executions> </plugin> -->
<plugin>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
@@ -152,61 +128,17 @@
</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 the webapp folder
-->
<!-- <profiles>
<profile>
<id>default-first</id>
<build>
<plugins>
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<executions>
<execution>
<id>install node and npm</id>
<phase>none</phase>
</execution>
<execution>
<id>npm install</id>
<phase>none</phase>
</execution>
<execution>
<id>npm run build</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>default-second</id>
<build>
<plugins>
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<executions>
<execution>
<id>install node and npm</id>
<phase>none</phase>
</execution>
<execution>
<id>npm install</id>
<phase>none</phase>
</execution>
<execution>
<id>npm run build</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles> -->
<!-- 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 the webapp folder -->
<!-- <profiles> <profile> <id>default-first</id> <build> <plugins> <plugin> <groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId> <executions> <execution> <id>install node and npm</id>
<phase>none</phase> </execution> <execution> <id>npm install</id> <phase>none</phase> </execution> <execution>
<id>npm run build</id> <phase>none</phase> </execution> </executions> </plugin> </plugins> </build> </profile>
<profile> <id>default-second</id> <build> <plugins> <plugin> <groupId>com.github.eirslett</groupId> <artifactId>frontend-maven-plugin</artifactId>
<executions> <execution> <id>install node and npm</id> <phase>none</phase> </execution> <execution> <id>npm
install</id> <phase>none</phase> </execution> <execution> <id>npm run build</id> <phase>none</phase>
</execution> </executions> </plugin> </plugins> </build> </profile> </profiles> -->
<properties>
<!-- util -->