Page History
...
Code Pro | ||
---|---|---|
| ||
custom-ee/ ├── custom-ee-webapp │ ├── pom.xml │ └── src └── pom.xml |
Line 3:
custom-ee/custom-ee-webapp/pom.xml
is the pom file of your custom webapp.Expand title Click to see a possible example Code Pro language xml title custom-ee/custom-ee-webapp/pom.xml linenumbers true <?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" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>com.example</groupId> <artifactId>custom-ee</artifactId> <version>1.0-SNAPSHOT</version> <relativePath>../pom.xml</relativePath> </parent> <artifactId>custom-ee-webapp</artifactId> <name>custom-ee: webapp</name> <packaging>war</packaging> <dependencies> <dependency> <groupId>info.magnolia.eebundle</groupId> <artifactId>magnolia-enterprise-pro-webapp</artifactId> <type>war</type> </dependency> <dependency> <groupId>info.magnolia.eebundle</groupId> <artifactId>magnolia-enterprise-pro-webapp</artifactId> <type>pom</type> </dependency> </dependencies> <build> <plugins> <plugin> <artifactId>maven-war-plugin</artifactId> <configuration> <!-- exclude jars copied "physically" from the webapp overlay - so we only get those resolved by Maven's dependency management --> <dependentWarExcludes>WEB-INF/lib/*.jar</dependentWarExcludes> </configuration> </plugin> </plugins> </build> </project>
- Line 5:
custom-ee/pom.xml
is the "parent pom file" of your custom webapp - this file is managing the dependencies and its versions.
...
- This parent pom file
Anchor | ||||
---|---|---|---|---|
|
...
Overview
Content Tools