[
https://issues.apache.org/jira/browse/IGNITE-10073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074597#comment-17074597
]
Pavel Tupitsyn edited comment on IGNITE-10073 at 4/3/20, 1:53 PM:
------------------------------------------------------------------
I thought about this a lot before, especially regarding Thin Client, which does
not need JAR files at all.
I see two solutions:
* Separate package, same as current, but without JAR files
The problem is with dependencies, such as Apache.Ignite.Linq. They still
depend on the main package with jar files, so the problem is not solved.
* Separate package for JAR files, included only when needed
This breaks existing users, and breaks "easy to get started" scenario
None of that looks good to me. The use case from the ticket description seems
to be rare. It is not hard to remove unneeded files as part of the
publish/build script.
was (Author: ptupitsyn):
I thought about this a lot before, especially regarding Thin Client, which does
not need JAR files at all.
# I see two solutions:
# Separate package, same as current, but without JAR files
The problem is with dependencies, such as Apache.Ignite.Linq. They still
depend on the main package with jar files, so the problem is not solved.
# Separate package for JAR files, included only when needed
This breaks existing users, and breaks "easy to get started" scenario
None of that looks good to me. The use case from the ticket description seems
to be rare. It is not hard to remove unneeded files as part of the
publish/build script.
> .NET: Add 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: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, sbcf
> Attachments: ignite-10073-vs-2.8.patch
>
>
> 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
(v8.3.4#803005)
