Re: java.util.logging and Maven builds
It is all a nightmare which will be resolved by retirement. :-P On the bright side, you could be committing PHP all day long. From: Paul Hoadley Date: Tuesday, June 27, 2017 at 4:42 PM To: Chuck Hill Cc: WebObjects Development , Hugi Thordarson Subject: Re: java.util.logging and Maven builds Hi Chuck, On 28 Jun 2017, at 03:59, Chuck Hill 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
Re: java.util.logging and Maven builds
It is all a nightmare which will be resolved by retirement. :-P On the From: Paul Hoadley Date: Tuesday, June 27, 2017 at 4:42 PM To: Chuck Hill Cc: WebObjects Development , Hugi Thordarson Subject: Re: java.util.logging and Maven builds Hi Chuck, On 28 Jun 2017, at 03:59, Chuck Hill 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
Re: java.util.logging and Maven builds
Hi Chuck, On 28 Jun 2017, at 03:59, Chuck Hill 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
Re: java.util.logging and Maven builds
Hi Paul, 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. Chuck From: Paul Hoadley Date: Monday, June 26, 2017 at 8:32 PM To: WebObjects Development Cc: Hugi Thordarson , Chuck Hill Subject: Re: java.util.logging and Maven builds For the archives: On 24 Jun 2017, at 10:18 am, Paul Hoadley mailto:pa...@logicsquad.net>> wrote: If you'd like, here's a workaround: You can force maven to copy the java resources (or certain resources). But of course, this is less than optimal. https://gist.github.com/hugith/a2ece8632ab33b994403ff9a04722fc1 Thanks Hugi I’ll check that out. Unbelievably, that’s not the complete fix. That copies logging.properties into the root of the application’s JAR, but java.util.logging _still_ doesn’t automatically find it. It allows me to change this startup parameter: -Djava.util.logging.config.file="Contents/Resources/logging.properties” to this: -Djava.util.logging.config.file=logging.properties at which point I think that's as good as we’re going to get. (I’ve never used java.util.logging before, and now I know why!) -- 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
