[jira] [Commented] (JDO-706) No enhancer log output with maven 2

[Michelle Caisse (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233168#comment-13233168
 ] 

Michelle Caisse commented on JDO-706:
-

The approach suggested to solving this problem is to manually add the log4j jar 
file to the class loader used to invoke JdoHelper.getEnhancer(ClassLoader) and 
to remove it from the project dependencies, so that log4j.properties file will 
be found in the root directory of the class loader used to load log4j. I have 
been able to make this approach work in a test environment; however, it entails 
removing springframework from the dependencies as well, since it has log4j as a 
transitive dependency. (To verify this, run mvn -X jdo-exectck:enhance.) I need 
input on how to proceed.

 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

[jira] [Commented] (JDO-706) No enhancer log output with maven 2

[Craig L Russell (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233182#comment-13233182
 ] 

Craig L Russell commented on JDO-706:
-

From reading the log4j code, there are two places that log4j looks for the 
log4j.properties: the loader that loaded log4j itself; and the context class 
loader.

We might have to look into the context class loader as the source for the 
log4j.properties. 


 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