Targets of mases.jnet.targets shall be renamed with a name that is specific for this project

[masesdevelopers]

Currently the missing JAR is not a direct problem for KEFCore, however the latest version of JNet introduced, with #479, a check on needed JARs and the issue is raised.
The missing JAR is related to the import chain of *.targets files, i.e. JNet defines a mases.jnet.targets with the following content:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <ItemGroup>
    <jnet_jars Include="$(MSBuildThisFileDirectory)\jars\*.*" />
  </ItemGroup>

  <Target Name="CopyFilesNative" BeforeTargets="Build">
    <Copy SourceFiles="@(jnet_jars)" DestinationFolder="$(TargetDir)\jars" />
  </Target>
  
  <Target Name="CopyFilesNativePublish" BeforeTargets="Publish">
    <Copy SourceFiles="@(jnet_jars)" DestinationFolder="$(PublishDir)\jars" />
  </Target>
</Project>

and KNet defines a mases.knet.targets with the following content:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <ItemGroup>
    <knet_jars Include="$(MSBuildThisFileDirectory)\jars\*.*" />
    <knet_config Include="$(MSBuildThisFileDirectory)\config\*.*" />
    <knet_configKraft Include="$(MSBuildThisFileDirectory)\config\kraft\*.*" />
  </ItemGroup>

  <Target Name="CopyFilesNative" BeforeTargets="Build">
    <Copy SourceFiles="@(knet_jars)" DestinationFolder="$(TargetDir)/jars" />
    <Copy SourceFiles="@(knet_config)" DestinationFolder="$(TargetDir)/config" />
    <Copy SourceFiles="@(knet_configKraft)" DestinationFolder="$(TargetDir)/config/kraft" />
  </Target>
  
  <Target Name="CopyFilesNativePublish" BeforeTargets="Publish">
    <Copy SourceFiles="@(knet_jars)" DestinationFolder="$(PublishDir)/jars" />
    <Copy SourceFiles="@(knet_config)" DestinationFolder="$(PublishDir)/config" />
    <Copy SourceFiles="@(knet_configKraft)" DestinationFolder="$(PublishDir)/config/kraft" />
  </Target>
</Project>

From both files it is possible to highlight that Targets have the same name, so chaining the *.targets the latest one replace the previous one.
Replacing lacally the Targets of mases.jnet.targets with another name the build chain works fine.
So, to avoid confusion Targets of mases.(jnet/knet).targets shall be renamed with a name that is specific for each project.

Originally posted by @masesdevelopers in masesgroup/KEFCore#268 (comment)