[jira] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: (was: jdo706.patch)
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
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: jdo706.patch
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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: 20120410-211429.zip
I get the same errors with java 1.6.0_25. Error log files attached.
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
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo706.patch
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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: jdo706.patch
Runs with errors. 11/91 configurations fail. 7 failures, 34 errors out of 1724
tests. Repeated error:
Error moving implementation log file Failed to delete original file
'C:\jdo_newest\datanucleus.txt' after copy to
'C:\jdo_newest\tck\target\logs\...-jdori.txt'
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
Attachments: jdo706.patch, jdo706.patch
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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: jdo706.patch
Uploading a patch for safekeeping. This doesn't yet work, but I think it's
close.
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
Attachments: jdo706.patch
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] [Updated] (JDO-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse updated JDO-708: Comment: was deleted (was: Wondering what the benefit is of this change over the existing setup?) Create JIRA component entry for exectck parent-pom modules -- Key: JDO-708 URL: https://issues.apache.org/jira/browse/JDO-708 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too. -- 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
