You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andreas Korneliussen (JIRA)" <de...@db.apache.org> on 2006/06/29 12:33:31 UTC
[jira] Resolved: (DERBY-1444) Using -Djvmflags option causes
NoClassDefFoundError
[ http://issues.apache.org/jira/browse/DERBY-1444?page=all ]
Andreas Korneliussen resolved DERBY-1444:
-----------------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
Resolving the issue since the patch has been committed to both trunk and 10.1 branch.
> Using -Djvmflags option causes NoClassDefFoundError
> ---------------------------------------------------
>
> Key: DERBY-1444
> URL: http://issues.apache.org/jira/browse/DERBY-1444
> Project: Derby
> Type: Bug
> Components: Test
> Versions: 10.1.3.0, 10.2.0.0
> Environment: Suns jvm 1.5
> Reporter: Vemund Østgaard
> Assignee: Vemund Østgaard
> Priority: Minor
> Fix For: 10.1.3.1, 10.2.0.0
> Attachments: 1444-diff, 1444-diff.stat
>
> When starting tests with the -Djvmflags option, the harness (RunList class) places "" around the argument to -Djvmflags when executing the java launcher to start a new jvm. This is (at least by suns java launcher) interpreted as a Class and not as a command line option, because of the "". Because of this I get a NoClassDefFoundError.
> I believe this is a problem that happens only when using Suns java launcher.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira