Hi Tarush, I think having a common folder where to put user lib that end up in the final deployable jar would be useful. This should be doable by tweaking just the pom file.
For SAMOA-31 however, the static reference is not really used, and can safely be removed, I think. Cheers, -- Gianmarco On Sun, Feb 21, 2016 at 6:56 PM, tarush grover <[email protected]> wrote: > Hi Nicolas, > > I was discussing about an issue : > > https://issues.apache.org/jira/browse/SAMOA-31 > > Regards, > Tarush > > On Sat, Feb 20, 2016 at 8:56 PM, Nicolas Kourtellis <[email protected] > > > wrote: > > > Hi Tarush, > > > > Can you please clarify what you mean by "common lib directory for all the > > jars"? > > > > If you refer to a common lib directory for developing new ML techniques > on > > top of a given DSPE, then you can probably focus on the classes found in > > the folder "samoa-api/". > > > > However, the purpose of SAMOA is to also provide connectors with > different > > DSPEs. So if you want to play with these apis, then you can look into the > > classes found in the folders "samoa-storm", "samoa-flink", "samoa-samza", > > "samoa-s4", or for local testing you can look into "samoa-local". > > > > If you manage to compile your version and you just want to call things > from > > the command line, then you can find the appropriate compiled jar files in > > the "target" folder. > > > > I hope this helps you proceed! > > > > Cheers, > > > > Nicolas > > > > > > > > > > On Sat, Feb 20, 2016 at 3:41 PM, tarush grover <[email protected]> > > wrote: > > > > > Hi All, > > > > > > Can we have a common lib directory where we can put all the jars and > take > > > reference of that common folder. > > > > > > Regards, > > > Tarush > > > > > > > > > > > -- > > Nicolas Kourtellis > > >
