You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Mariia Mykhailova (JIRA)" <ji...@apache.org> on 2015/10/01 20:52:30 UTC

[jira] [Updated] (REEF-640) Create CLI CPP project Org.Apache.REEF.ClrDriver. Phase I

     [ https://issues.apache.org/jira/browse/REEF-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mariia Mykhailova updated REEF-640:
-----------------------------------
    Fix Version/s: 0.13

> Create CLI CPP project Org.Apache.REEF.ClrDriver. Phase I
> ---------------------------------------------------------
>
>                 Key: REEF-640
>                 URL: https://issues.apache.org/jira/browse/REEF-640
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF Driver
>            Reporter: Beysim Sezgin
>            Assignee: Beysim Sezgin
>             Fix For: 0.13
>
>
> Currently CLR driver is started by java driver. This is problematic for CLR when for looking for assemblies to load as it would look at %JAVA_HOME%\bin.  So we manage our own assembly loading by using AppDomain.AssemblyResolve event. This works but gets us into assembly versioning business. Better to sandwich wrap java with DotNet Driver so that CLR itself can manage assembly loading. 
> Phase I: This JIRA,  is for creating the CLI C++ project Org.Apache.REEF.ClrDriver  which will take the same parameters as produced by JavaLaunchCommandBuilder pass them thru to java using JNI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)