You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Chenxi Zhao (JIRA)" <ji...@apache.org> on 2018/06/01 20:55:00 UTC
[jira] [Comment Edited] (REEF-2030) Azure Batch Client Errors due
to Shaded Jars in the local directory
[ https://issues.apache.org/jira/browse/REEF-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498524#comment-16498524 ]
Chenxi Zhao edited comment on REEF-2030 at 6/1/18 8:54 PM:
-----------------------------------------------------------
[~rogan] This error happens after rebasing REEF-1991 Delete old project, rename DotNet projects to old project names patch in master. I realized this and have fixed this when I rebased my PR [https://github.com/apache/reef/pull/1468]. Commit 3 ([https://github.com/apache/reef/pull/1468/commits/2da33e1c1a1bf8a0a7fb5dbefe2a804ced4b1c2d])was to fix this.
was (Author: homezcx):
[~rogan] This error happens after rebasing [REEF-1991] Delete old project, rename DotNet projects to old project names patch in master. I realized this and have fixed this when I rebased my PR [https://github.com/apache/reef/pull/1468]. Commit 3 was to fix this.
> Azure Batch Client Errors due to Shaded Jars in the local directory
> -------------------------------------------------------------------
>
> Key: REEF-2030
> URL: https://issues.apache.org/jira/browse/REEF-2030
> Project: REEF
> Issue Type: Bug
> Components: REEF.NET Client
> Reporter: Rogan Carr
> Priority: Major
> Labels: usability
>
> After using the Azure Batch Client, two REEF jars will remain in the current working directory of the user:
> `reef-bridge-client-0.17.0-SNAPSHOT-shaded`
> `reef-bridge-java-0.17.0-SNAPSHOT-shaded`
> When run a second time from this directory, the following error is thrown:
> `...\reef\global\reef-bridge-client-0.17.0-SNAPSHOT-shaded.jar' already exists., 'System.IO.IOException'`
> The solution is to clean these files up after the REEF directory structure is set up and populated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)