[
https://jira.jboss.org/browse/JBDS-1268?page=com.atlassian.jira.plugin.sy...
]
Will Dinyes commented on JBDS-1268:
-----------------------------------
Since this is not a Bug, there's no Steps To Reproduce section, so I'll add that
as a comment:
Steps To Reproduce:
1. Install JBDS 3 normally, with "java -jar jbdevstudio-3.0.0.GA.jar"
- note the $INSTALL_DIR used.
2. Once install is completed, copy InstallConfigRecord.xml from $INSTALL_DIR to user's
home directory
3. Uninstall JBDS 3 via shortcut
4. Re-run install with "java -jar jbdevstudio-3.0.0.GA.jar
~/InstallConfigRecord.xml"
5. Note that the install runs without prompts, and installs to $INSTALL_DIR, but no other
customizations are included, and no shortcuts are created.
Request: Complete Automated Install using XML
---------------------------------------------
Key: JBDS-1268
URL:
https://jira.jboss.org/browse/JBDS-1268
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 3.0.0.GA
Environment: Java 1.6 (Sun), RHEL 5.5
Reporter: Will Dinyes
Attachments: InstallConfigRecord.xml
Currently, the install process outputs an InstallConfigRecord.xml file, which for a
general IzPack install, would contain all the information needed to repeat the install in
exactly the same way, but without prompts.
However, the output file does not currently contain all the required info. The only
sections included are the install path, and JBDS short cut panel. When using this file to
perform an automated install via:
java -jar jbdevstudio-3.0.0.GA.jar InstallConfigRecord.xml
The install goes to the right directory, but the short cut does not appear to be
created.
It would be great if this file could be used to automate an installation. In my
particular case, the reason is that we will have instructors and students doing weekly
installs of the software, and if we could streamline that process, it would free up more
time for learning how to use the dev tools (which are great, by the way).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira