In your case the file associations are essentially broken, hence it launches 7-Zip instead of the system default JVM.

Can you please perform those exact steps?

1. launch a console
2. type java -version
3. report to us the output (you can also take a screenshot directly using JIRA).

I'm interested to see this as I need to know if we can improve how Jar installer are launched using izpack2exe, or if this issue is not relevant.

Thanks a lot!

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\marvin>java -version
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode, sharing)

C:\Documents and Settings\marvin>

On my file association I have 7-zip as default and java as alternative.

I had already installer (going to temp and open .jar with java), but I believe is a good improvement.

VELO

Thanks for reporting back. This indeed needs a fix, I think it will just turn down to using java -jar as the command rather than trying to open the Jar.

Here is a possible patch to fix the problem.

Martin, could you please test it on your side?

Where can I download to test?

VELO

Marvin,

You need to:

1. apply the patch yourself (attached to this issue in JIRA). It requires a Python environment to work as it patches the izpack2exe.py file.
2. run izpack2exe over any IzPack-based installer to get a .exe
3. try it and see if it fixes it.

In case you don't have that, I'll prepare a Win32 executable of izpack2exe for you tomorrow.

Cheers

I will need that...

Python 4 me is some kind of snake =D

VELO

This attachment contains a Python-free Win32 executable to wrap a IzPack installer Jar.

Could you please try it to wrap an installer, and test it on your machine?

Thanks a lot.

There was a missing file.

Here what I did:

1. Downloaded the latest stable IzPack release
2. Packed with the izpack2exe executable in dist.zip
3. Tested successfuly.

I just need your confirmation to close the issue

On a Windows VISTA box with a normal Java6 installation, it appeared that running 'java -jar installer.jar' would fail. The old behavior (opening the Jar) did not have such problems.

Because this issue is caused by a non-standard file type association, I am re-opening it and will revert the fix in the next few days.

Please comment if you have a better solution.

The patch has been reverted.