Thanks for responding Bobby.

Ramin, my team has worked with some other Bloomberg engineers on the
Storm-on-Mesos project where we are particularly impacted by the long
classpaths of Storm.  Are you using Storm-on-Mesos or regular Storm?   We
have backported the change of STORM-2191 to Storm v1.0.6, and there is a
build I created manually in my GitHub fork of Storm:


This custom Storm build has been used to create the Storm-on-Mesos builds
for v1.0.6.

If you're using v1.0.6 you can use that custom build directly, or you can
take the changes and port them to whichever Storm version you are using and
rebuild it.


- Erik

On Thu, Apr 5, 2018 at 11:05 AM, Bobby Evans <> wrote:

> Sorry this is a late reply.
> There is no way to switch the classpath over to wildcards without changing
> the code in
> In newer versions of storm that has been done.  You can see
> <>
> for more details about it.
> Thanks,
> Bobby
> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
>> wrote:
>> Hi,
>> when Storm runs, it sets up the command line with full path of all jars
>> to be included in the classpath.
>> How can I simplify the command line by specifying directories and
>> wildcard where the jars reside?
>> In doing that, does Storm care about the order of the jars in cp?

Reply via email to