[#IZPACK-44] ~ directory is not understood - jira.codehaus.org

IzPack

~ directory is not understood

Created: 26/Mar/08 01:10 PM Updated: 07/Apr/08 03:50 PM Resolved: 06/Apr/08 04:52 AM

Return to search

Component/s:

Installer, Panels

Affects Version/s:

3.11.0

Fix Version/s:

4.0.0

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. ss1.jpg
(32 kB)

2. ss2.jpg
(35 kB)

Environment:

Linux Kubuntu 6.10, JRE 1.6.0

Description

« Hide

When selecting installation directory to something like "~/myDirectory", the installation is not done in the home directory (didn't figure if it is actually created nor where). All the remaining installation goes smoothly and we get a success message afterwards.

Sort Order:

[ Permalink | « Hide ]

Julien Ponge added a comment - 27/Mar/08 05:54 PM

We would need more details for this issue to understand what really happens.

If you can, adding some related screenshots would probably help.

Thanks

[ Permalink | « Hide ]

bflorat added a comment - 28/Mar/08 08:51 AM

See provided screenshots. From ~, I launch java -jar /data/download/jajuk-java-installer-1.5.1_RC5.jar
I enter "_{/jajuk-test", it is replaced by "/home/bflorat/}/jajuk-test" instead of "/home/bflorat/jajuk-test"

[ Permalink | « Hide ]

Julien Ponge added a comment - 02/Apr/08 03:05 AM

It looks like this is a JDK issue as it doesn't expand '~' in file paths, isn't it?

[ Permalink | « Hide ]

Julien Ponge added a comment - 06/Apr/08 04:52 AM

Lucky you, I have transformed this JDK-issue into an IzPack improvement

[ Permalink | « Hide ]

Julien Ponge added a comment - 06/Apr/08 04:52 AM

The fix is in the latest SVN trunk. Bertrand, could you please check it for yourself and confirm so that I close the issue?

[ Permalink | « Hide ]

bflorat added a comment - 07/Apr/08 03:48 PM

Thx for fixing Julien. Sorry, testing IzPack trunk version is not possible for us as we use at jajuk a complex continous integration system and not from desktops: it's too mush work and risk to upgrade. Please considere it as fixed, we'll check it when using next IzPack stable release and reopen if required.