Right, that's the -P option I mentioned :)
But you have to either:
1) Remember to pass in -P (aka --properties) on the cmdline when running standalone.sh
2) You have to edit standalone.conf so -P is passed in by default (we can edit this during
build time)
or
3) You have a custom "hawkular.sh" script that runs "standalone.sh -P
hawkular.properties"
My initial gut feeling is to do 2.
----- Original Message -----
I think you nailed it...
On Fri, Jan 29, 2016 at 3:39 PM, John Doyle < jdoyle(a)redhat.com > wrote:
You can do this:
$JBOSS_HOME/bin/standalone.sh --properties=$JBOSS_HOME/my-jboss.properties
Maybe I'm oversimplifying?
On Fri, Jan 29, 2016 at 9:16 AM, Thomas Heute < theute(a)redhat.com > wrote:
Yes, it's what I hoped for (but really have no idea if that can work).
On Fri, Jan 29, 2016 at 3:06 PM, Juraci Paixão Kröhling <
jpkroehling(a)redhat.com > wrote:
The advantage I see in managing the properties inside standalone.xml is
that it can be managed via Wildfly CLI and compatible tools. Perhaps
even with future versions of Hawkular.
Unless there's a way to tell Wildfly to load the system properties from
a separate file. This would be the best of two worlds.