[jboss-jira] [JBoss JIRA] (AS7-1947) Startup options jboss.domain.base.dir / jboss.domain.config.dir are ignored

[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on AS7-1947: ---------------------------------------- @The log property won't most likely not be reflected, since the startup script does not understand java properties. AS7-1947 seems to be related to that. (from AS7-1850) boot.log for host-controller and process-controller are created under domain/log because domain.sh/.bat scripts can't reflect java properties. I think there are two ways: * parse arguments within .bat/.bash scripts {code} ## Properties from -D parameter for var in "$@" do echo "$var" if [[ $var == -Djboss.domain.log.dir=* ]]; then echo "OK -- `echo $var | sed 's/-Djboss.domain.log.dir=//'`" fi done {code} {code} ## Properties from file . property_file echo $prop ## but problems with jboss.domain.log.dir :( unusable {code} {code} ## Properties from file for var in `cat test.properties` do echo "$var" if [[ $var == jboss.domain.log.dir=* ]]; then echo "OK -- `echo $var | sed 's/jboss.domain.log.dir=//'`" fi done {code} Something similar should be developed for Windows but I'm not sure if it's possible at all. I checked commands for 'cmd' [1] and I couldn't find something similar to sed. Command findstr can be used as grep substitute. * introduce LOG_PATH + CONFIGURATION_PATH properties as described in AS7-2494 I vote for LOG_PATH + CONFIGURATION_PATH properties [1] http://ss64.com/nt/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira