reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chenxi Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-2030) Azure Batch Client Errors due to Shaded Jars in the local directory
Date Tue, 19 Jun 2018 18:27:00 GMT

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

Chenxi Zhao commented on REEF-2030:
-----------------------------------

[https://github.com/apache/reef/pull/1468] is merged, which fixes 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
>            Assignee: Chenxi Zhao
>            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)

Mime
View raw message