db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-706) No enhancer log output with maven 2
Date Sun, 06 May 2012 20:09:48 GMT

    [ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269273#comment-13269273

Michael Bouschen commented on JDO-706:

I get different results when running the latest patch on WIndows. Only pmf.conf is failing
for applicationidentity and datastoreidentity:
  Total tests run: 1798. Failures: 0, Errors: 8.
  2 of 117 configurations failed.
When running on mac all configurations pass.

It looks like with the patch the datanucleus log file is generate with the expected filename
(e.g. app-jdoql-datanucleus.txt). I think this is the reason for the error messages:
Error moving implementation log file Source '/Users/mbouschen/Projects/JDO/workspace/jdo/trunk/datanucleus.txt'
does not exist
> 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

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


View raw message