[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

[Pavel Tupitsyn (Jira)]

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

Pavel Tupitsyn commented on IGNITE-10554:
-

Merged to master: 20b3fb8450196215b0ccda38ac8dee7963c14fa3

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has 
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
>  in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application 
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR 
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to 
> the output folder.
> Test cases:
> * .NET 4.x
> * .NET Core 2.x, 3.x Windows & Linux
> * LINQPad
> * Binary zip distribution (examples, .NET Core examples)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

[Igor Sapego (Jira)]

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

Igor Sapego commented on IGNITE-10554:
--

Looks good to me.

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has 
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
>  in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application 
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR 
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to 
> the output folder.
> Test cases:
> * .NET 4.x
> * .NET Core 2.x, 3.x Windows & Linux
> * LINQPad
> * Binary zip distribution (examples, .NET Core examples)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

[Ignite TC Bot (Jira)]

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

Ignite TC Bot commented on IGNITE-10554:


{panel:title=Branch: [pull/6954/head] Base: [master] : Possible Blockers 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4674452]]
* IgniteCacheWithIndexingTestSuite: 
CacheRegisterMetadataLocallyTest.testClientFindsValueByAffinityKeyDynamicCacheWithoutExtraRequest
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Activate / Deactivate Cluster{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4674389]]
* IgniteStandByClusterSuite: 
IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers_5_Clients_FromClient
 - Test has low fail rate in base branch 0,0% and is not flaky

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4674499&buildTypeId=IgniteTests24Java8_RunAll]

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has 
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
>  in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application 
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR 
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to 
> the output folder.
> Test cases:
> * .NET 4.x
> * .NET Core 2.x, 3.x Windows & Linux
> * LINQPad
> * Binary zip distribution (examples, .NET Core examples)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

[Pavel Tupitsyn (Jira)]

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

Pavel Tupitsyn commented on IGNITE-10554:
-

[~mmuzaf] yes, the patch is coming soon, we definitely should include this in 
2.8.

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.8
>
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has 
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
>  in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application 
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR 
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to 
> the output folder.
> Test cases:
> * .NET 4.x
> * .NET Core 2.x, 3.x Windows & Linux
> * LINQPad
> * Binary zip distribution (examples, .NET Core examples)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

[Maxim Muzafarov (Jira)]

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

Maxim Muzafarov commented on IGNITE-10554:
--

[~ptupitsyn]

Hello, any updates on this issue? Should we include it to 2.8 release?

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.8
>
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has 
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
>  in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application 
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR 
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to 
> the output folder.
> Test cases:
> * .NET 4.x
> * .NET Core 2.x, 3.x Windows & Linux
> * LINQPad
> * Binary zip distribution (examples, .NET Core examples)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

[Connor Adams (JIRA)]

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

Connor Adams commented on IGNITE-10554:
---

I think this might be linked to another issue IGNITE-4980.

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.8
>
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)