Message-ID: <1251824075.1167.1427662532792.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1166_1522619561.1427662532791" ------=_Part_1166_1522619561.1427662532791 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
It is a good idea to collect your files and assets into the Mave= n project where your POM file resides.
Bearing in mind that a maven clean command will delete the target folder= , we will not put anything there that we want preserved.
You are free to put things in any structure that you want but we make th= e fillowing suggestion.
We will put our files that we want included in a src folder tree.
Under src, we will create a main sub-folder and under that will create a= izPack folder which will be the root of the files for the installation.
You need to create an install.xml file that describes how you want your = installation package to be built. We will discuss the content of this file = in great detail later on.
For now we can create the initial <installation> = entry to get started
This gives us the following folder structure.
Under the scr/main/izpack, you can create folders to ho= ld the various files that you want to include in your installation.
These might include:
imagesfor splash pages and other bitmap = images
aboutfor product descriptions
In order to make life easier when these file locations need to be specif=
ied in the install.xml, we can befine a variable
that will point to the
We will discuss variables in more detail in the Variables Section.
Another, more Maven-centric approach is pulling in the base directory (a=
nd other useful values) directly from a Maven property defined in the POM a=
nd accessing them by expressions of kind
nbsp;in install.xml, as described in Properties.