[izpack-dev] Installer skeleton and Eclipse run configuration

[René Krell]

Hi all,

is there any smart way for making a run configuration for compiling a test
package. At the moment, the installer skeleton is taken from lib/installer.jar
(Packager.writeSkeletonInstaller()) and not from the freshly compiled classes
from rebuilding the workspace after local changes.

Thus, there is always a two-phase run configuration necessary at the moment_
1. Creating the skeleton jars (using Ant and build.xml)
2. Compiling

Does anyone have a better solution?

BTW: I don't like the way how native IzPack jars and 3rd-party jars are mixed
together under libs, they should be separated.

I would appreciate a smarter way for creating the skeleton for debugging
purposes, maybe I'll find some... ;-)

R.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[René Krell]

I think I have some workaround for Eclipse:
Project Properties - Builder - Add a new Ant builder "Create skeletons" with:
Buildfile:
${workspace_loc:/IzPack/src/build.xml}
using the default target "all".

Not so efficient but does the job within the given circumstances.

On Tuesday 24 November 2009 11:47:28 you wrote:
> ...

> is there any smart way for making a run configuration for compiling a test
> package. At the moment, the installer skeleton is taken from
> lib/installer.jar (Packager.writeSkeletonInstaller()) and not from the
> freshly compiled classes from rebuilding the workspace after local
> changes.
>
> Thus, there is always a two-phase run configuration necessary at the
> moment_ 1. Creating the skeleton jars (using Ant and build.xml)
> 2. Compiling
>
> Does anyone have a better solution?

> ...