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 Wed, 24 Feb 2016 15:43:18 GMT

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

Pavel Tupitsyn edited comment on IGNITE-1626 at 2/24/16 3:42 PM:
-----------------------------------------------------------------

How to test:
* Run Ignite Platform .NET NuGet build on TC: http://204.14.53.151/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNetNuG
* Download build artifact (nupkg file)
* Visual Studio:
** Make sure NuGet is installed: https://docs.nuget.org/consume/installing-nuget
** Create a new C# console application
** Switch to x64 build configuration
** In Package Manager Console: {code}Install-Package Apache.Ignite.NET -Source <path-to-nupkg-FOLDER>{code}
This should produce no errors (red text).
** Add namespace import: {code}using Apache.Ignite.Core;{code}
** Run simple code to verify that Ignite starts: {code} using (var ignite = Ignition.Start())
{ignite.CreateCache<int, int>("test").Put(1, 1); }{code}
* LINQPad:
** Download *AnyCPU* LINQPad from http://www.linqpad.net/Download.aspx
** Run, hit F4, Add NuGet
** Discard warning
** Settings -> Add package source pointing to a folder with nupkg file, close settings
** Select your new package source from combobox at the bottom
** Install Apache.Ignite.NET package
** Switch query to Statements, paste and run {code} using (var ignite = Ignition.Start())
{ignite.CreateCache<int, int>("test").Put(1, 1); }{code}
** Verify samples: in the left pane, click Samples, nuget, Apache.Ignite.NET


was (Author: ptupitsyn):
How to test:
* Run Ignite Platform .NET NuGet build on TC: http://204.14.53.151/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNetNuG
* Download build artifact (nupkg file)
* Visual Studio:
** Make sure NuGet is installed: https://docs.nuget.org/consume/installing-nuget
** Create a new C# console application
** Switch to x64 build configuration
** In Package Manager Console: {code}Install-Package Apache.Ignite.NET -Source <path-to-nupkg-FOLDER>{code}
This should produce no errors (red text).
** Run simple code to verify that Ignite starts: {code} using (var ignite = Ignition.Start())
{ignite.CreateCache<int, int>("test").Put(1, 1); }{code}
* LINQPad:
** Download *AnyCPU* LINQPad from http://www.linqpad.net/Download.aspx
** Run, hit F4, Add NuGet
** Discard warning
** Settings -> Add package source pointing to a folder with nupkg file, close settings
** Select your new package source from combobox at the bottom
** Install Apache.Ignite.NET package
** Switch query to Statements, paste and run {code} using (var ignite = Ignition.Start())
{ignite.CreateCache<int, int>("test").Put(1, 1); }{code}
** Verify samples: in the left pane, click Samples, nuget, Apache.Ignite.NET

> .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
>
>
> *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)

Mime
View raw message