You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kukushkin (JIRA)" <ji...@apache.org> on 2018/10/30 23:56:00 UTC
[jira] [Assigned] (IGNITE-10073) Ignite NuGet package without
embedded Ignite JARs
[ https://issues.apache.org/jira/browse/IGNITE-10073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kukushkin reassigned IGNITE-10073:
-----------------------------------------
Assignee: Alexey Kukushkin
> Ignite NuGet package without embedded Ignite JARs
> -------------------------------------------------
>
> Key: IGNITE-10073
> URL: https://issues.apache.org/jira/browse/IGNITE-10073
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 2.6
> Reporter: Alexey Kukushkin
> Assignee: Alexey Kukushkin
> Priority: Major
>
> The existing Apache.Ignite NuGet package includes Ignite JARs deployed into the "libs" directory in the .NET project output directory upon the package installation.
> We prefer using external Ignite JARs from $IGNITE_HOME/libs instead of the JARs in the local libs directory.
> Right now we have to manually remove local "libs" directory after every Apache.Ignite package installation or upgrade.
> It would help us having another Ignite NuGet package without the embedded Ignite JARs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)