Ryan Shoemaker - JavaSoft East wrote:
> JAXB is using Kohsuke's sfx4j[1] utility to produce the bundles and it
> looks like the code is kicking off a new java process:
>
> https://sfx4j.dev.java.net/source/browse/sfx4j/sfx4j/src/Setup.java?rev=1.4&view=auto&content-type=text/vnd.viewcvs-markup
>
> // build command line
> List cmds = new ArrayList();
> cmds.add("java");
> cmds.add("-jar");
> cmds.add(jar.toString());
> cmds.addAll(Arrays.asList(args));
>
> // launch java
> Process proc = Runtime.getRuntime().exec((String[]) cmds.toArray(new String[cmds.size()]));
> new Thread(new Setup(System.in,proc.getOutputStream(),false)).start();
> new Thread(new Setup(proc.getInputStream(),System.out,true)).start();
> new Thread(new Setup(proc.getErrorStream(),System.err,true)).start();
> System.exit(proc.waitFor());
Right, but for that to fail, the thing that's kicked from it (in our
case our installer) needs to be built for Tiger, which it shouldn't be.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com