For the archives: On 24 Jun 2017, at 10:18 am, Paul Hoadley <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 >> <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
