storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonas Krauß <>
Subject Re: Avoid building jar after every change is made during development
Date Tue, 22 Aug 2017 14:09:49 GMT

have a look at

You can use that in your main method and run the topology class as a java app. A common approach
is to check if command line args are empty and then use local mode (if not empty you are most
probably submitting the topology on the cluster and state the topology name as a command line



On Aug 22, 2017, at 3:38 PM, Leonardo Ferreira <> wrote:

> Hi, 
> I am brand new to Apache Storm and I am starting to feel painful the need to build the
entire jar file after every change I make during development process to test the changes that
were made.
> Is there a way to perform sort of a "hot deploy" with no need to build the entire jar
file ?
> Thanks!
> -- 
> Leonardo Ferreira
> Software Developer

View raw message