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

Michael Bouschen commented on JDO-706:
--------------------------------------

I can run jdo-706.patch on Mac w/o any errors:
  Total tests run: 1798.
  All (117) configurations passed.

However, on Windows I also see errors on pmf test and other test 
configurations. 
For some reason not all test configurations are executed. The summary at the 
bottom of the TCK-results.txt file lists less tests and less configurations:
  Total tests run: 1417. Failures: 0, Errors: 8.
  2 of 82 configurations failed.
During the mvn install run I see errors on the commad line:
*> Running tests for pm.conf with datastoreidentity on 'derby' mapping= ... 
Exception on command [java, -cp, 
/D:/users/michael/.m2/repository/org/apache/jdo/jdo-exectck/1.0-SNAPSHOT/jdo-exectck-1.0-SNAPSHOT.jar;/D:/users/michael/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar;...
These tests do not occur in TCK-results.txt and there are no log files for 
these tests.

Any idea what is different on Windows?
                
> 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

        

Reply via email to