project_key: JBPAPP6 Right now the installer accepts an "automation" mode where you can feed it an automation xml file. That will run the installer without any need for user interaction. e.g java -jar installer.jar <automation file> Right now that automation file has to be located in the same server as where the installer.jar is found. One improvement would be to move the automation file to some server, so that all the machines where installer.jar will be used will use the SAME automation file. Syntax could be: java -jar installer.jar http://<server>/automation.xml or java -jar installer.jar ftp://<server>/automation.xml Right now I think that http and ftp should be the minimum that we can support. I also don't think that we need user authentication for now for http /ftp.
This could also be a good component to be upstreamed to Izpack 4.3 / Izpack 5.
Link: Added: This issue is a dependency of JBPAPP-9555
http://git.app.eng.bos.redhat.com/?p=izpack.git;a=commit;h=23b8dd94ad1f02b50ae65f1a1b5e36a0f00cf350
Docs QE Status: Removed: NEW
@Jyoti please change fix version to exact EAP version in which this fix is available instead of tbd eap6 for ease of QA verification.
This will appear in 6.2.0. The assignee was set incorrectly and thus was missed.
Verified on EAP 6.2.0.ER1
I would say this should be public. I agree with Petr, and I would also want this new feature to be in the release notes as well, because it is a powerful and useful feature. +1 to making this bug public.