[jira] [Commented] (REEF-1255) Specify packages shared between projects on solution level

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

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

Markus Weimer commented on REEF-1255:
-------------------------------------

I agree with the goal of the JIRA. However, so far I used the Visual Studio UI to make sure NuGet dependencies are in sync across projects.When you right-click on a Solution and select "Manage NuGet Packages", the resulting dialog has a "Consolidate tab" that shows when different projects depend on different versions of the same dependency. Granted, this is not as elegant as the POM inheritance in Maven, but it seems to be the canonical way to do this in .NET. What would we gain by doing the above? I am asking because it sounds like a lot of careful manual work to maintain a structure with a central {{packages.config}}.

> Specify packages shared between projects on solution level
> ----------------------------------------------------------
>
>                 Key: REEF-1255
>                 URL: https://issues.apache.org/jira/browse/REEF-1255
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Mariia Mykhailova
>            Priority: Minor
>
> It would be nice to specify versions of packages used in multiple .NET projects not in each project's {{packages.config}} in a single place, so that we don't run into issues with different projects using different versions, like REEF-1015. One step further is to declare all packages in solution-level {{packages.config}} and eliminate project-level files altogether.



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