[izpack-devel] IZPACK_HOME for the compiler (packager)

[Bartz, Klaus]

Hi Fabrice,
sorry for indirect addressing...
I think it should be documented in the chapter where compiling
will be described. Whether there are other places or not, I do not
know. 
I do also not know whether "my" for steps are to much technical
or not. Now it will run also automatically (autoresolve of
IZPACK_HOME). I do not really know whether there are constallations
where the automatic do not run, but at least existent ways should
be preserved.
important is, that now an Exception will be raised if the test file
cannot be found. Therefore at an existent IZPACK_HOME and
throwing the first step should be to lock, why the testfile (
ShellLink.dll) not found. Will be good, if this is documented.


Will be nice if you can make the docu :-)

Cheers

Klaus


>-----Original Message-----
>From: izpack-devel-bounces at lists.berlios.de
>[mailto:izpack-devel-bounces at lists.berlios.de]On Behalf Of Miraodb
>Sent: Monday, August 07, 2006 4:49 PM
>To: izpack-devel at lists.berlios.de
>Subject: Re: [izpack-devel] IZPACK_HOME for the compiler (packager)
>
>
>Hi Klaus,
>
>First of all, Thanks  for taking care of that!
>Also, i want to know i you see any new/update docu that i 
>should write ?
>Is the 4 steps good enough or will we be missing something ?
>
>Cheers,
>Fabrice
>----- Original Message ----- 
>From: "Bartz, Klaus" <Klaus.Bartz at coi.de>
>To: <izpack-devel at lists.berlios.de>
>Sent: Monday, August 07, 2006 3:29 PM
>Subject: [izpack-devel] IZPACK_HOME for the compiler (packager)
>
>
>> Hi all,
>> yesterday there was a problem thread on the user list
>> (problem creating shortcuts) which was based on a 
>> missing IZPACK_HOME. I do not know why anything run,
>> but the handling of the home dir was really not
>> optimal.
>> I have just checked in a patch into trunk. Now
>> with the "normal" compiler
>> 
>> 1. the -DIZPACK_HOME procedure works already
>> 2. there is no the comandline argument -h "Path"
>> 3. If 1. and 2. are not exist or take no valid path
>>    the compiler tries to resolve the path depending
>>    on the jar file or class path which contains the
>>    Compiler class file.
>> 4. If 1. - 3. results no valid path, an exception 
>>    will be thrown.
>> 
>> A valid path is a path where the subpath
>> bin/native/izpack/ShellLink.dll exist.
>> 
>> With the standalone-compiler only 1. and 2. will
>> be perfomed. If no valid path was found "." will
>> be assumed. If this is not correct, please fix it
>> (the person who knows where the IZPACK_HOME path
>> should link using the standalone-compiler).
>> See CompilerConfig.java line 1896.
>> 
>> Cheers 
>> 
>> Klaus
>> _______________________________________________
>> izpack-devel mailing list
>> izpack-devel at lists.berlios.de
>> http://bat.berlios.de/mailman/listinfo/izpack-devel
>> 
>> 
>_______________________________________________
>izpack-devel mailing list
>izpack-devel at lists.berlios.de
>http://bat.berlios.de/mailman/listinfo/izpack-devel
>