On 27. 5. 2015, at 13:11, Max Rydahl Andersen
On 27 May 2015, at 10:51, Martin Malina wrote:
>> On 26. 5. 2015, at 20:31, Max Rydahl Andersen <manderse(a)redhat.com> wrote:
>> On 26 May 2015, at 18:39, Rob Stryker wrote:
>>> When using dl-runtimes to install DV or FSW, it runs the installer
>>> The installer jar does not respect the installation path the user set
>>> the dl-runtimes wizard. It can't, obviously, bc we never transmit it
>>> the installer at all.
>>> It'd be great if we could agree on some sysprop we can set when
>>> java -jar dv-6.1-installer.jar such that the installer checks it for a
>>> default installation folder.
>>> Any ideas who I would ping over getting something like that
>>> on the runtimes side?
>> I don't think you'll ever be able to find a global agreement on it.
>> A) start by opening feature request against the installer - in this case
>> TEIID or Data Virtualisation product.
>> B) if the installer is a izpack based installer there might be ways to
>> do it already:
>> Try with java -DINSTALL_PATH=/opt/myplace -jar myinstaller.jar to
>> see if that works ?
> Unfortunately it doesn't work.
> For JBDS installer jar, running
> java -jar installer.jar -options-template myinstaller.properties
> generates the property file, but it's empty.
> For DV, running the same command, the resulting property file includes
"INSTALL_PATH=" which should indicate that you can set this property as Max
> But running the installer with
> java -DINSTALL_PATH=/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 -jar
> it will still offer this as the default path:
> So no luck here.
sounds like a bug we should fix on both sides ;)
care to open them ?
for JBDS (although we're not gonna install
JBDS from within JBDS, it may still be a good thing to have there)