[jira] [Commented] (REEF-255) Org.Apache.REEF.Bridge.JAR does not re-copy the JARs upon cleaning of the packages

["Markus Weimer (JIRA)" <ji...@apache.org>]

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

Markus Weimer commented on REEF-255:
------------------------------------

[This issue|http://nuget.codeplex.com/workitem/2094] seems to be related. They closed it as "by design". Hence, we might need a different approach. Maybe we can copy the jars out of the {{packages}} folder as part of the build? That way we wouldn't have to install them into the project. The challenge then becomes finding the {{packages}} folder reliably. 

> Org.Apache.REEF.Bridge.JAR does not re-copy the JARs upon cleaning of the packages
> ----------------------------------------------------------------------------------
>
>                 Key: REEF-255
>                 URL: https://issues.apache.org/jira/browse/REEF-255
>             Project: REEF
>          Issue Type: Bug
>          Components: NuGet, REEF.NET
>    Affects Versions: 0.10
>            Reporter: Markus Weimer
>
> {{Org.Apache.REEF.Bridge.JAR}} doesn't behave as expected with regards to binary files in the project: The NuGet copies the jar files from the {{packages}} folder into the project folder and adds a reference to the project upon package installation. However, it does not do so upon re-installation of the NuGet packages. To reproduce, follow these steps:
>   1. Add {{Org.Apache.REEF.Bridge.JAR}} as a NuGet to a project.
>   2. Clean the solution.
>   3. Exit VS and delete the {{packages}} folder as well as all {{jar}} files.
>   4. Open Visual Studio and trigger a build, which will fail
> This is annoying because it basically suggests that users should add the .{{.jar}} files to their repository. It would be better for our NuGets to re-install cleanly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)