Re: [jboss-dev] Logging & bootstrap integration branch merged

It depends when we want the logging service to be started. I guess, the best time would be to start the logging service as soon as the bootstrap is done so that the logging service can capture and log as much information as possible. I agree with the "config-deploy" sort of necessity which might be required going forward (or i think it will get addressed if we move to the system-apps-deploy folder sort of thing that we discussed some time back). But i guess in case of the logging-service, it still would be too late because we would have either lost or would be difficult to configure the logging for the "deployers" since the logging service would start after the "deployers".

As far as the logging service is concerned, i guess this would make sense (i.e. leaving it in conf/). The earlier version of the logging service (which used jboss-log4j.xml) worked around the redeploy/reconfigure issue by setting up a Log4jTimerServiceTask which was a timer task (default 60 sec.) which would pick up the changes to the logging configuration file. Maybe we could do something similar?