[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234145#comment-13234145
]
Craig L Russell commented on JDO-706:
-------------------------------------
Can you try creating a class loader that has the log4j.properties (nothing
else) and set it as the context class loader? I don't think anything else in
the enhancer depends on the context class loader. The exectck creates a class
loader from which to load the enhancer implementation, and then exectck passes
another class loader to the enhancer implementation that contains the classes
and metadata to enhance. So replacing the context class loader should be
innocuous in this context.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log
> properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
