[
https://issues.apache.org/jira/browse/IGNITE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1626:
---------------------------------------
Attachment: linqPad5.png
> .Net: Create NuGet package.
> ---------------------------
>
> Key: IGNITE-1626
> URL: https://issues.apache.org/jira/browse/IGNITE-1626
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vasilisa Sidorova
> Priority: Blocker
> Fix For: 1.6
>
> Attachments: linqPad5.png
>
>
> *Overview*
> To boost usage of the product we need to distribute it using NuGet, which is
> tightly integrated with Visual Studio.
> To achieve this several technical, infrastructure and marketing tasks must be
> completed.
> *Technical tasks*
> - Apache Ignite.NET heavily depends on relative positions of compiled Java
> classes. We must be able to apply different classpath search strategies
> depending on packaging. This includes normal search in exploded build
> directory, search in NuGet package, search in local Maven repo.
> - We need a way to select classpath search strategy. E.g. we can add special
> marker resource to NuGet package so that DLL understands that it is
> NuGet-based. More investigation here is reuqired.
> - Minimal set of required JARs should be defined. Currently we have over
> >100Mb of Java libraries shipped with Ignite build. NuGet has limitation of
> 30Mb per package. Only vital subset of JARs should be shipped.
> - Resulting package should be tested automatically on TC
> *Infrastructure tasks*
> - INFRA team must be asked about a place where NuGet package could be stored.
> - Separate build plan should be created, producing NuGet artifacts.
> *Marketing tasks*
> - We need to produce clean, selling and intriguing header and description for
> our package and attach logo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
