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 2016/03/02 13:13:18 UTC

[jira] [Commented] (IGNITE-2740) .NET: IGNITE_HOME resolution restricts custom deployment

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

Pavel Tupitsyn commented on IGNITE-2740:
----------------------------------------

* Removed exception on failed IGNITE_HOME resolve (it was added incorrectly as part of IGNITE-1626).
* Added documentation: https://apacheignite-net.readme.io/docs/deployment

IGNITE-1626 also introduced another way: put jars into "libs" folder near Apache.Ignite.Core.dll. We can add that to the documentation after release.

> .NET: IGNITE_HOME resolution restricts custom deployment
> --------------------------------------------------------
>
>                 Key: IGNITE-2740
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2740
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Blocker
>             Fix For: 1.6
>
>
> Need to make sure that users may deploy Ignite JARs with their applications in any way they want.
> Currently we have quite restrictive checks in IgniteHome.IsIgniteHome method.
> Documentation should also be updated with "Deployment" page.



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