[
https://issues.apache.org/jira/browse/IGNITE-10073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074599#comment-17074599
]
Pavel Tupitsyn commented on IGNITE-10073:
-----------------------------------------
`Apache.Ignite.targets` file is responsible for jar file copy procedure. We can
introduce a condition there, so that users can disable jar copy by adding a
property to their .csproj file like this:
{code}
<PropertyGroup>
<IgniteSkipJarFileCopy>true</IgniteSkipJarFileCopy>
</PropertyGroup>
{code}
Thoughts?
> .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)
