| File | Date | Author | Commit |
|---|---|---|---|
| .gitignore | 2020-04-29 |
|
[fc5c70] [configuration] Ignore target directory |
| README-ES.md | 2020-05-02 |
|
[bfe2d1] [documentation] Add README |
| README.md | 2020-05-02 |
|
[bfe2d1] [documentation] Add README |
| pom.xml | 2023-03-24 |
|
[b6115c] [release] version 0.0.10 |
[EN] [ES]
It is recommended to use maven overlay, to create a war project to include the dependencies and configuration files required by the project.
In the dependencyManagement section, add the net.sf.aguacate.aguacate-bom artifact, importing it as pom, specifying the required version (see here available versions).
<dependencyManagement>
<dependencies>
<dependency>
<groupId>net.sf.aguacate</groupId>
<artifactId>aguacate-bom</artifactId>
<version>0.0.4</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
The maven-war-plugin configuration is added. Indicate in the overlay section the artifact net.sf.aguacate.aguacate.
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>3.2.2</version>
<configuration>
<overlays>
<overlay>
<groupId>net.sf.aguacate</groupId>
<artifactId>aguacate</artifactId>
</overlay>
</overlays>
</configuration>
</plugin>
</plugins>
</build>
In the dependencies section, add the dependency net.sf.aguacate.aguacate, with scope runtime and typewar, without version.
<dependencies>
<dependency>
<groupId>net.sf.aguacate</groupId>
<artifactId>aguacate</artifactId>
<type>war</type>
<scope>runtime</scope>
</dependency>
</dependencies>
An example of this configuration is in the file pom.xml of the project aguacate-demo.