[
https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3446:
----------------------------------
For now, would a workaround for JBIDE-20914 (making the jbds-dist-diff script support
headless install) be to create a /Applications/jbdevstudio folder with the correct
permissions? Then we could tweak the script to move the CONTENTS of the folder rather than
the whole folder.
Or, what if the jbds-dist-diff script creates the folder and sets the correct write perms
before doing the console install? Or could the script detect the OS and if OSX, prompt the
user to run the install as root?
Of course, the best / most flexible solution would be to be able to set the install path
via commandline (because then we could push into /tmp/ instead of ~/ or /Applications/)
but would any of the above workarounds work in the short-term?
Add support for IzPack INSTALL_PATH property to predefine
installation path
---------------------------------------------------------------------------
Key: JBDS-3446
URL:
https://issues.jboss.org/browse/JBDS-3446
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 8.1.0.GA
Reporter: Martin Malina
Assignee: Denis Golovin
Fix For: 10.x
In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports
supplying properties to the installer, so that some values are predefined.
Details are here:
http://docs.codehaus.org/display/IZPACK/Unattended+Installations
The idea is that you could run this:
java -DINSTALL_PATH=/default/path -jar installer.jar
And this would pre-fill the installation path to the path given in the command.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)