Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Wed, 3 Aug 2016 19:15:20 +0000 (UTC)
From: "Julia (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12950091.1457994367000.215795.1470251720781@Atlassian.JIRA>
In-Reply-To: <JIRA.12950091.1457994367000@Atlassian.JIRA>
References: <JIRA.12950091.1457994367000@Atlassian.JIRA> <JIRA.12950091.1457994367800@arcas>
Subject: [jira] [Commented] (REEF-1255) Specify packages shared between
 projects on solution level
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 03 Aug 2016 19:15:22 -0000


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

Julia commented on REEF-1255:
-----------------------------

Original idea is to reduce the places/out of sync when changing a version number, such as version of Josn. But looks like using solution level packages.config also introduced some inconvenience when using VS to manage NeGet references. 

> 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)