<div dir="ltr">I started some "spec" here: <a href="https://docs.google.com/document/d/1Q2wFKlp_-cI8k56k7YURxbqAShQxDsSD5tusW5LQ2PY/edit">https://docs.google.com/document/d/1Q2wFKlp_-cI8k56k7YURxbqAShQxDsSD5tusW5LQ2PY/edit</a><div><br></div><div>please comment / edit</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 16, 2015 at 2:46 PM, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> right, interactive installer is another approach. Currently, you can actually<br>
> reuse the same jar and use the<br>
> --wildfly-home=/path/to/your/wildfly/home to change the path, not sure if the<br>
> param takes precedence before the property files though, Mazz can shed some<br>
> light here.<br>
<br>
</span>Correct. The way the installer works is every setting you see in the .properties file can be overridden by installer cmdline options (not just wildfly home).<br>
<span class=""><br>
><br>
> ok, in that case, everything could be optional in the UI and if the wf-home<br>
> is not filled in the property files, nor passed as the param, the installer<br>
> can ask in the bash. This sounds good.<br>
<br>
</span>Right now if there is no wildfly home in the properties or as a cmdline option, the installer fails.<br>
<br>
Installer does not use Aesh. Sounds like we have to switch to using that before we go further with installer commandline enhancements.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>