You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "Anupam (JIRA)" <ji...@apache.org> on 2016/02/09 04:00:22 UTC

[jira] [Comment Edited] (REEF-1197) Fix REEF .NET build concurrency issues around JAR creation and NuGet cleanup

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

Anupam edited comment on REEF-1197 at 2/9/16 2:59 AM:
------------------------------------------------------

Moving to [Visual Studio 2015|https://issues.apache.org/jira/browse/REEF-313] is blocked by this issue as the build concurrency is exacerbated in VS 2015 (for unknown reasons).


was (Author: anupam128):
Moving to Visual Studio is blocked by this issue as the build concurrency is exacerbated in VS 2015 (for unknown reasons).

> Fix REEF .NET build concurrency issues around JAR creation and NuGet cleanup
> ----------------------------------------------------------------------------
>
>                 Key: REEF-1197
>                 URL: https://issues.apache.org/jira/browse/REEF-1197
>             Project: REEF
>          Issue Type: Bug
>            Reporter: Anupam
>            Assignee: Anupam
>
> We have certain build concurrency issues where non-explicit dependency across projects cause build failures when Visual Studio executes build with maximum parallelism for a machine.
> Further there are some build actions like JAR generation and copying which are required by only one project but are invoked in every project via build.props. This leads to unnecessary concurrency.



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