You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/08/06 22:13:05 UTC
[jira] [Resolved] (REEF-255) Org.Apache.REEF.Bridge.JAR does not
re-copy the JARs upon cleaning of the packages
[ https://issues.apache.org/jira/browse/REEF-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Weimer resolved REEF-255.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.12
Resolved via [REEF-494].
> 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
> Assignee: Beysim Sezgin
> Fix For: 0.12
>
>
> {{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)