It is all a nightmare which will be resolved by retirement. :-P On the
From: Paul Hoadley <pa...@logicsquad.net> Date: Tuesday, June 27, 2017 at 4:42 PM To: Chuck Hill <ch...@gevityinc.com> Cc: WebObjects Development <webobjects-dev@lists.apple.com>, Hugi Thordarson <h...@karlmenn.is> Subject: Re: java.util.logging and Maven builds Hi Chuck, On 28 Jun 2017, at 03:59, Chuck Hill <ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote: What you are describing seems to be the intent of this part of Java: If "java.util.logging.config.class" property is not set, then the "java.util.logging.config.file" system property can be used to specify a properties file (in java.util.Properties format). The initial logging configuration will be read from this file. If neither of these properties is defined then, as described above, the LogManager will read its initial configuration from a properties file "lib/logging.properties" in the JRE directory. I did not see any mention of a default file name or location, other than the JRE one. Thanks for doing my research for me! That would seem to explain everything. Well, everything except that Eclipse seems to pick up logging.properties from src/main/resources, which must be what set my expectation for how things would work in deployment. Unless I imagined even that. I’ve moved on. I’m putting this episode behind me… -- Paul Hoadley http://logicsquad.net/ https://www.linkedin.com/company/logic-squad/
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
