You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Antoine Tran (Jira)" <ji...@apache.org> on 2022/11/29 17:29:00 UTC
[jira] [Commented] (STORM-3533) Make a distinct storm-ras artifact
[ https://issues.apache.org/jira/browse/STORM-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640861#comment-17640861 ]
Antoine Tran commented on STORM-3533:
-------------------------------------
Up. Even in storm 2.4.0, RAS classes are present in storm-server but not storm-client. We would like to avoid storm-server as dependencies for our topology users.
> Make a distinct storm-ras artifact
> ----------------------------------
>
> Key: STORM-3533
> URL: https://issues.apache.org/jira/browse/STORM-3533
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-client, storm-core, storm-server
> Affects Versions: 2.0.0
> Environment: CentOs 7.7
> Storm 2.0.0
> Maven 3.5.3
> OpenJdk 8
> Reporter: Antoine Tran
> Priority: Minor
>
> Storm 2.0.0 release page [here|http://storm.apache.org/2019/05/30/storm200-released.html] suggest us to put storm-server as test scope for testing. But RAS packages are in storm-server package too, and we need it when we launch our topology. Some of RAS packages should be either integrated in storm-core or in a distinct package storm-ras, so that we do not have to put storm-server as compile test, which we do for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)