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

JAVA-15409: Fix formatting of POMs (#12992)

Browse Source
This commit is contained in:
freelansam
2022-11-18 00:26:06 +05:30
committed by GitHub
parent 178aed574e
commit 5bfbf38f59
62 changed files with 235 additions and 214 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistence-modules/deltaspike/pom.xml
+23 -20
View File
@@ -18,20 +18,23 @@
<dependencyManagement>
<dependencies>
<!-- for junit5 to successfully be able to discover junit4 tests, we need 4.12+ version of
junit:junit in the classpath. hence forcing the latest 4.13.2 available version for junit5 compatibility -->
<!-- for junit5 to successfully be able to discover junit4 tests, we need 4.12+ version of -->
<!-- junit:junit in the classpath. hence forcing the latest 4.13.2 available version for -->
<!-- junit5 compatibility -->
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<!-- JBoss distributes a complete set of Java EE 7 APIs including a Bill of Materials (BOM).
A BOM specifies the versions of a "stack" (or a collection) of artifacts. We use this here so that we
always get the correct versions of artifacts. Here we use the jboss-javaee-7.0-with-tools stack (you
can read this as the JBoss stack of the Java EE 7 APIs, with some extras tools for your project, such
as Arquillian for testing) and the jboss-javaee-7.0-with-hibernate stack you can read this as the JBoss
stack of the Java EE 7 APIs, with extras from the Hibernate family of projects) -->
<!-- JBoss distributes a complete set of Java EE 7 APIs including a Bill of Materials (BOM). -->
<!-- A BOM specifies the versions of a "stack" (or a collection) of artifacts. -->
<!-- We use this here so that we always get the correct versions of artifacts. -->
<!-- Here we use the jboss-javaee-7.0-with-tools stack (you can read this -->
<!-- as the JBoss stack of the Java EE 7 APIs, with some extras tools for your project, such -->
<!-- as Arquillian for testing) and the jboss-javaee-7.0-with-hibernate stack -->
<!-- you can read this as the JBoss -->
<!-- stack of the Java EE 7 APIs, with extras from the Hibernate family of projects) -->
<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>jboss-javaee-7.0-with-tools</artifactId>
@@ -57,16 +60,16 @@
</dependencyManagement>
<dependencies>
<!-- First declare the APIs we depend on and need for compilation. All of them are provided by
JBoss WildFly -->
<!-- First declare the APIs we depend on and need for compilation. -->
<!-- All of them are provided by JBoss WildFly -->
<!-- Import the CDI API, we use provided scope as the API is included in JBoss WildFly -->
<dependency>
<groupId>javax.enterprise</groupId>
<artifactId>cdi-api</artifactId>
<scope>provided</scope>
</dependency>
<!-- Import the Common Annotations API (JSR-250), we use provided scope as the API is included
in JBoss WildFly -->
<!-- Import the Common Annotations API (JSR-250), we use provided scope -->
<!--as the API is included in JBoss WildFly -->
<dependency>
<groupId>org.jboss.spec.javax.annotation</groupId>
<artifactId>jboss-annotations-api_1.2_spec</artifactId>
@@ -117,16 +120,16 @@
<artifactId>hibernate-jpamodelgen</artifactId>
<scope>provided</scope>
</dependency>
<!-- Annotation processor that raising compilation errors whenever constraint annotations are
incorrectly used. -->
<!-- Annotation processor that raising compilation errors -->
<!--whenever constraint annotations are incorrectly used. -->
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator-annotation-processor</artifactId>
<scope>provided</scope>
</dependency>
<!-- Optional, but highly recommended -->
<!-- Arquillian allows you to test enterprise code such as EJBs and Transactional(JTA) JPA from
JUnit/TestNG -->
<!-- Arquillian allows you to test enterprise code such as -->
<!--EJBs and Transactional(JTA) JPA from JUnit/TestNG -->
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
@@ -215,8 +218,8 @@
</dependencies>
<build>
<!-- Maven will append the version to the finalName (which is the name given to the generated
war, and hence the context root) -->
<!-- Maven will append the version to the finalName -->
<!-- (which is the name given to the generated war, and hence the context root) -->
<finalName>${project.artifactId}</finalName>
<plugins>
<plugin>
@@ -256,8 +259,8 @@
<profiles>
<profile>
<!-- An optional Arquillian testing profile that executes tests in your WildFly instance -->
<!-- This profile will start a new WildFly instance, and execute the test, shutting it down
when done -->
<!-- This profile will start a new WildFly instance, and execute the test, -->
<!-- shutting it down when done -->
<!-- Run with: mvn clean test -Parq-wildfly-managed -->
<id>arq-wildfly-managed</id>
<dependencies>