Commit Graph

11 Commits

Author SHA1 Message Date
R. Tyler Croy a505e9c5c8
Rely on our file path containing stormjar.jar in order to determine if we're ina supervisor
This is admittedly a bit hackish but I have yet to find any data at runtime
that indicates whether we're executing inside of a local mode (non jar) or
clustered mode other than this

Fixes #16
2015-09-11 15:18:25 -07:00
R. Tyler Croy a0249a7d7a
Executing on a supervisor via a bolt/etc we must set up the embedded env properly
The main() function isn't going to be executed when the topology is sent over
to the cluster, redstorm/environment will be loaded properly on
supervisor-based execution however, so mucking with these globals there seems
like a reasonable approach

References #12
2015-09-11 10:53:21 -07:00
Ian Smith cf723b2136 rescue DEFAULT_STORM_CONF_FILE = File.expand_path('~/.storm/storm.yaml') so we can use redstorm in environments that don't have HOME set. 2014-11-02 09:07:49 -08:00
Colin Surprenant 6f1854a6ee cleanup constants & environment 2013-07-24 23:07:03 -04:00
Colin Surprenant 59093baf57 issue #82 - make configurable the javac source/target version 2013-06-18 15:02:10 -04:00
Colin Surprenant 1cf0fae5f9 do not mess with gem paths for specs 2012-06-28 18:03:50 -04:00
Colin Surprenant 7113768dc4 always set gem path/home in target 2012-06-28 17:31:44 -04:00
Colin Surprenant a988abd1b9 refactored Ruby version tokens handling 2012-06-28 13:19:03 -04:00
Colin Surprenant 0195dca16c refactored --1.8/--1.9 ruby version handling 2012-06-26 17:53:33 -04:00
Colin Surprenant ac95f71e43 refactored environment settings 2012-06-26 16:06:29 -04:00
Colin Surprenant 9c0b41af43 reworked env and path settings, debug traces 2012-06-05 15:08:01 -04:00