You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/03/11 00:55:38 UTC

[jira] [Commented] (REEF-194) Remove 3rd party libraries from REEF Client Nuget

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

Markus Weimer commented on REEF-194:
------------------------------------

[~chris.douglas] and I spoke offline. It is probably fine to keep the JAR in our NuGets. I suggest to do the following:

 # Make a NuGet for our native and managed bridge DLLs. Probably {{Org.Apache.REEF.Bridge.dll}}
 # Make a NuGet that contains *only* the shaded JAR {{reef-bridge-java-0.11.0-incubating-SNAPSHOT-shaded.jar}}

That way we cleanly separate our code from the code we redistribute.

[~chris.douglas], does this sound like a clean plan? Any Apache rules we need to be aware off when it comes to 3rd party binaries in our binary drops?

> Remove 3rd party libraries from REEF Client Nuget
> -------------------------------------------------
>
>                 Key: REEF-194
>                 URL: https://issues.apache.org/jira/browse/REEF-194
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF.NET
>            Reporter: Markus Weimer
>            Assignee: Beysim Sezgin
>
> Currently, the REEF Client NuGet package contains the shaded REEF JAR. The latter in turn contains all the dependencies of the Java side of REEF. We shouldn't do this and instead provide the user with means to download those dependencies themselves.



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