[
https://issues.apache.org/jira/browse/STORM-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Tran updated STORM-3533:
--------------------------------
Description: 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. (was: 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.)
> 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.3.4#803005)
