We need you!


The IzPack documentation needs work, and you are invited to edit it!

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »


The CompilePanel can be used to compile Java source code that is being installed.

This panel must appears after xxxx panel to be sure that the code is available for compilation.

The details for the compilation are specified using the resource CompilePanel.Spec.xml. Need explanation and example showing how the panel is linked to the Compile.Spec.xml resource or is it done magically

Example of a  CompilePanel.Spec.xml file that offers a choice of 2 compilers and includes 2 compilation tasks.


CompilePanel.Spec.xml resource example

Actually, jobs can be nested. Why do you want to do that? How do you nest them?

A change to the classpath within a job only affects this job and nested jobs. The classpath should be specified before any files or directories.

Compilation elements



compilerThis section lists the choices of compilers that can be used to compile the sources 


Jobs element

The <jobs> element contains  a <classpath> element and one or more <job> elements.

The <classpath> element at the <jobs> level applies to nested <job> tasks.  


Jobs can have an optional name attribute which is used to document the task's role.

Jobs can have the following nested elements.


User Interaction

The user can change the compiler to use and choose from some default compilation options before the compilation is started.



Resource NameDescription
This code appears above. This description should be about setting the resource up to point to the file.



 <choice value="..." />
 <choice value="..." />
 <classpath add="..."/>
 <job name="optional name">
 <directory name="..." />
 <packdependency name="some package name"/>
 <classpath sub="..."/>
 <file name="..." />
 </job> ...
  • No labels