You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/22 19:27:06 UTC
[jira] [Updated] (STORM-1992) Deploy multilang-javascript code as
node package
[ https://issues.apache.org/jira/browse/STORM-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated STORM-1992:
----------------------------------
Labels: pull-request-available (was: )
> Deploy multilang-javascript code as node package
> ------------------------------------------------
>
> Key: STORM-1992
> URL: https://issues.apache.org/jira/browse/STORM-1992
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-multilang
> Affects Versions: 1.0.1
> Reporter: Marc Zbyszynski
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Now that storm includes Flux, it is easier than ever to deploy a topology with javascript components. If the Bolt and Spout base classes defined in storm/multi-lang/javascript were available in a node.js package on https://www.npmjs.com/ it would allow node.js storm users to take advantage of node's built in package manager to develop their own bolts and spouts.
> It would be relatively trivial to add some maven tasks to storm/multi-lang/javascript/pom.xml to take the storm.js resource and package it in a node module and submit it to npm.
> This could be added to the pom as a separate profile so it wouldn't impact the normal storm build process.
> This integration will also make it easier to add unit tests for storm.js
> For additional background see this discussion:
> http://mail-archives.apache.org/mod_mbox/storm-dev/201607.mbox/%3CCAD8EKPHc6O1LCnoQUUoYoDuMQ3uSaNpD5gR4onK%2B0EL5_qcZ3Q%40mail.gmail.com%3E
> If this sounds like a worthwhile addition to the project I would be happy to submit a PR.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)