[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255701#comment-13255701
]
Michelle Caisse commented on JDO-706:
-------------------------------------
Andy's guess that the issues on Windows have to do with its limitation on
command length appears to be a good one. With a web search I find this, for
example:
"When I launch our application in Eclipse on Windows I receive the following
error:
Exception occured executing command line.
Cannot run program .. : CreateProcess error=87, The parameter is incorrect
I've solved this in the past by shortening the CLASSPATH.
I've now come to a point where I can no longer shorten the CLASSPATH, and would
like to know if there are any other workarounds.
http://support.microsoft.com/kb/830473 seems to indicate that the max command
prompt line length in windows xp is 8191 characters, and the only solution is
to shorten folder names, reduce depth of folder trees, using parameter files,
etc."
exectck displays the command line for each test, so we can check that and see
what might be truncated for the failing tests.
> 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
