You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/07/03 15:00:00 UTC
[jira] [Commented] (IGNITE-5628) .NET: incorrect jvm.dll lookup
paths for JRE
[ https://issues.apache.org/jira/browse/IGNITE-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072577#comment-16072577 ]
Pavel Tupitsyn commented on IGNITE-5628:
----------------------------------------
Fixed in master: {{5093660d758ad4149d5cd135f3cad3dfee0ae6e4}}
> .NET: incorrect jvm.dll lookup paths for JRE
> --------------------------------------------
>
> Key: IGNITE-5628
> URL: https://issues.apache.org/jira/browse/IGNITE-5628
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{jvm.dll}} is located in different subfolders in JRE and JDK. Current code only accounts for JDK. So if we set {{JAVA_HOME}} to a custom xcopy-deployed JRE folder, jvm.dll can not be found.
> With normal Windows installations it works because we use registry for that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)