[izpack-user] How to debug output from calling a .bat file when pack selected and .bat is calling java -jar <jarfile> <args>

[GizzPack]

If I have a .bat file that gets run when a pack is selected (using a condition and ProcessPanel.Spec.xml),

and the .bat file runs a java method (a method inside a jar that I am given and which uses log4j),

how do I see any exception or output (log4j, stderr, stdout) that the class spits out?

It looks like IzPack has suppressed all output from stderr, stdout (try catch, bury ?)

I put <logfiledir> in my ProcessPanel.Spec.xml and there is nothing (no log4j printouts) from the jar in the log file.

I can't even get a log file to be created in the first place, so that is not a solution.  And from googling around am led

to believe that stack traces from my jars would not be there anyway.

---

Also when I try to run IzPack in debug mode, I get an exception that it can't find an lang pack for english

so that is not a solution.  I only get the exception when I have a condition.  If I remove the condition no lang 

pack exception is thrown.

---

I can not modify the jar that I want to debug because it is a third part jar, so modifying the code there and writing to a file 

from within methods in the jar is not a solution either.

There is nothing in the console where IzPack was launched to indicate an exception thrown.

There is only an empty error dialog popped up by IzPack saying "Error (-)" and the dialog is void of any information.

The only lettering there is "Error".

At first glance, it appears that IzPack implementers went out of their way to surpress all stderr, stdout (stack traces)

from external jar files.

---

I can't put a break point and debug because I have not yet found a way to programitcally launch the installer and make it go.  If you have lines of java code that launch the installer and you have actually used it to launch the installer from within another java program (a unit test for example), please do post.

If you have any ideas that are 

   => direct from your actual implementation of running a bat file if a pack is selected and that .bat calls java -jar and it is a jar that was given to you that you can not modify and that jar threw an exception and you found a way to see the stack trace, then please let me know.  If not then you are just guessing.

This should not be hard to do and you would simply expect the stack trace to go to the window where you launched IzPack but for some reason, the decision was made to suppress this and make it impossible to get the information needed.