ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-1626) .Net: Create NuGet package.
Date Thu, 12 Nov 2015 16:18:10 GMT

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

Pavel  Tupitsyn edited comment on IGNITE-1626 at 11/12/15 4:17 PM:
-------------------------------------------------------------------

* nuspec file created to include all necessary JAR files, Apache.Ignite.Core.dll, and default
config file
* version is being set automatically from assemblyinfo
* IGNITE_HOME resolve logic adjusted to detect NuGet deployment
* Package tested locally: no extra steps from the user are required (besides Java installation).
Install package => Ignition.Start works.

* TC config created to build nupkg: http://94.72.60.102/viewType.html?buildTypeId=IgniteBuildsAndUploads_IgniteBuildFabricOnlyNet

> INFRA team must be asked about a place where NuGet package could be stored.
No need for this. Package is created by TC task, tested, and then pushed to nuget.org.

What is left:
* proper wording in summary and description
* icon


was (Author: ptupitsyn):
* nuspec file created to include all necessary JAR files, Apache.Ignite.Core.dll, and default
config file
* version is being set automatically from assemblyinfo
* IGNITE_HOME resolve logic adjusted to detect NuGet deployment
* Package tested locally: no extra steps from the user are required (besides Java installation).
Install package => Ignition.Start works.

* TC config created to build nupkg: http://94.72.60.102/viewType.html?buildTypeId=IgniteBuildsAndUploads_IgniteBuildFabricOnlyNet

> .Net: Create NuGet package.
> ---------------------------
>
>                 Key: IGNITE-1626
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1626
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: 1.5
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel  Tupitsyn
>            Priority: Blocker
>             Fix For: 1.6
>
>
> *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 have limitation of 30Mb per package. Only
vital subset of JARs should be shipped.
> *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)

Mime
View raw message