ends up initializing the LogManager before a system prop
like java.util.logging.config.file can be set.
If this sounds like it'd be worth capturing in an issue/JIRA, I could add
more detail, but first wanted to check this wasn't a known problem or a
usage error... (or if the "solution" is just not to fork which I wasn't
hoping to resort to yet).