[izpack-changes] [Bug #4735] "izpack" Ant task doesn't use "basedir" to find panel jars

[noreply at berlios.de]

Bug #4735, was updated on 2005-Aug-02 19:39
Here is a current snapshot of the bug.

Project: IzPack
Category: IzPack3
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: lpreston
Assigned to : bartzkau
Summary: "izpack" Ant task doesn't use "basedir" to find panel jars

Details: The Ant task "izpack" uses a "basedir" attribute to locate most resources, but does not do so for custom panel JAR files, which must be in a bin/panels directory either in the standalone-compiler.jar file, the IZPACK installation directory, or in the directory from which the Ant file is being run (the basedir of the Ant project). 

 It would be nice if the directory that is specified as the basedir to the task could be used as the root of this search as well, so users could have all their installation files colocated. 

After looking at the code, I was able to make a small change to Compiler.jar in the addPanels method to try a findProjectResource() call if the call to findIzPackResource() failed, which allowed me to locate the JARs in the basedir with the extended path of bin/panels.


Follow-Ups:

Date: 2006-Jan-03 16:29
By: rfallon

Comment:
I have found that this is also the case with the custom actions jars, e.g. RegistryInstallerListener. You have to have to run the ant file from the IzPack directory as the basedir parameter is ignored.
-------------------------------------------------------

Date: 2005-Aug-03 08:58
By: bartzkau

Comment:
Seems good... 
We must discuss it a little bit, 
please look into devel email list.
-------------------------------------------------------

For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=4735&group_id=1408