I haven't tried this directly, but you should be able to include metron-management onto the classpath for metron-common when executing the REPL via mvn exec:java: mvn exec:java -Dexec.mainClass="org.apache.metron.common.stellar.shell.StellarShell" -Dexec.args="-cp ../metron-management/target/metron-management-0.3.0.jar:%classpath" should work
I'd look more at the exec plugin docs, though, if it doesn't. Report back, because it'd be good to know (and put in the docs). :) On Thu, Nov 17, 2016 at 11:48 AM, Nick Allen <[email protected]> wrote: > Sorry a little trigger happy there. > > When developing a new Stellar function, I obviously want to be able to toy > with it in the REPL a little. When developing functions that live in > metron-common this is easy. I can just run StellarShell from my IDE and > since everything in metron-common is in the classpath, the new function is > found and life is good. > > On the other hand, when developing a function that lives somewhere else, > like metron-management, I have not found a way to run the REPL locally and > also add the other project (metron-management, in this case) to the > classpath so that it finds the function. > > When developing the KAFKA_* functions, I actually developed them in > metron-common and then when I was happy with them, I moved them to > metron-management. > > Has any found a better way to do this? > > > > On Thu, Nov 17, 2016 at 11:43 AM, Nick Allen <[email protected]> wrote: > > > > > > > -- > > Nick Allen <[email protected]> > > > > > > -- > Nick Allen <[email protected]> >
