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

Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 02:32:27 UTC

[jira] [Updated] (STORM-30) Modularized Storm artifacts for using Storm as a library

     [ https://issues.apache.org/jira/browse/STORM-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-30:
------------------------------
    Component/s: storm-core

> Modularized Storm artifacts for using Storm as a library
> --------------------------------------------------------
>
>                 Key: STORM-30
>                 URL: https://issues.apache.org/jira/browse/STORM-30
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: James Xu
>            Priority: Minor
>
> https://github.com/nathanmarz/storm/issues/313
> When using Storm as a library (for example, the DRPC client), storm-lib brings in a lot of dependencies you probably don't need, such as all the UI-related libraries. It would be nice if the build were more sophisticated, so that rather than have one giant storm-lib, you'd have dependencies for:
> Just the Thrift code + helpful wrapper like DRPCClient
> Storm itself
> The UI stuff
> Leiningen 2 may be able to do this via submodules



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