Lifecycle Mappings
...
| Configuration Attribute | Value Range | Default Value | Description |
|---|---|---|---|
baseDir | string | ${project.build.directory}/staging | Base directory of compilation process |
installFile | string | ${basedir}/src/main/izpack/install.xml | Location of the IzPack installation file. |
comprFormat | default | bzip2 | default | Target compression format of the compiled installer jar |
| comprLevel | integer -1, 0..9 | -1 | Compression level of the compiled installer jar. Deactivated by default (-1) |
outputDirectory | ${project.build.directory} | Target directory containing the compiled installer jar | |
mkdirs | true | false | false | Whether to automatically create parent directories of the output file |
finalName | Name of the compiled installer jar | ||
| classifier | Not set | Classifier to add to the artifact generated. If given, the artifact is attachable. Furthermore, the output file name gets -classifier as suffix. If this is not given,it will merely be written to the output directory according to the finalName. | |
| enableAttachArtifact | true | false | true | Whether to attach the generated installer jar to the project as artifact if a classifier is specified. This has no effect if no classifier was specified. |
enableOverrideArtifact | true | false | false | Whether to override the artifact file by the generated installer jar, if no classifier is specified. This will set the artifact file to the given name based on outputDirectory + finalName or on output. This has no effect if a classifier is specified. |
autoIncludeUrl | true | false | false | Whether to automatically include project.url from Maven into the IzPack info header |
autoIncludeDevelopers | true | false | false | Whether to automatically include developer list from Maven into IzPack info header |
kind | standard | web | standard | Resulting installer type |
...
Once you have run this goal, verify that all of the files are in the staging directory in the structure that you have described in your installation file.
Collecting your project's dependencies
If your application includes jars that can be specified as Maven dependencies, your POM file can use the Maven dependency plugin to get the latest versions from a Maven repository.
The dependencies must be listed as dependencies in the pom's dependency section.
| Code Block | ||
|---|---|---|
| ||
<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>
...
<!-- Launch IzPack automatically -->
<packaging>izpack-jar</packaging>
<properties>
<!-- Installer variables -->
<staging.dir>${project.build.directory}/staging</staging.dir>
<info.appName>My Killer Application</info.appName>
<info.appsubpath>my-killer-app/standard</info.appsubpath>
<izpack.dir.app>${basedir}/src/main/izpack</izpack.dir.app>
<staging.dir.app>${staging.dir}/appfiles</staging.dir.app>
</properties>
<dependencies>
<dependency>
<groupId>org.codehaus.izpack</groupId>
<artifactId>izpack-panel</artifactId>
<version>${my.izpackplugin.version}</version>
</dependency>
<dependency>
<groupId>com.example.myApp</groupId>
<artifactId>main</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>com.example.myApp</groupId>
<artifactId>core</artifactId>
<version>${project.parent.version}</version>
</dependency>
.....
</dependencies>
</project |
To get the dependencies into the staging structure, the Maven copy dependency plugin can be invoked.
| Code Block | ||
|---|---|---|
| ||
<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>
...
<!-- Launch IzPack automatically -->
<packaging>izpack-jar</packaging>
<properties>
<!-- Installer variables -->
<staging.dir>${project.build.directory}/staging</staging.dir>
<info.appName>My Killer Application</info.appName>
<info.appsubpath>my-killer-app/standard</info.appsubpath>
<izpack.dir.app>${basedir}/src/main/izpack</izpack.dir.app>
<staging.dir.app>${staging.dir}/appfiles</staging.dir.app>
</properties>
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.10</version>
<configuration>
<outputDirectory>${staging.dir}/lib</outputDirectory>
<excludeTransitive>true</excludeTransitive>
<stripVersion>true</stripVersion>
<overWriteReleases>true</overWriteReleases>
<overWriteSnapshots>true</overWriteSnapshots>
<overWriteIfNewer>true</overWriteIfNewer>
<excludeScope>system</excludeScope>
</configuration>
<executions>
<execution>
<id>copy</id>
<phase>process-resources</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
</build>
</project |
This tells Maven to find the dependencies listed in the <dependencies> section and copy then to the lib folder in the staging directory staging.dir.
It also specifies that the transitive dependencies are not to be copied (since in this case, they have been built into the jars already.
If you get an error resembling "maven-dependency-plugin (goals "copy-dependencies") is not supported by m2e. pom.xml ... Maven Project Build Lifecycle Mapping Problem", you can refer to this stackoverflow article for the fix.