All of them have been moved out already. They were moved out when we went to
the maven assembly plugin for packaging. Including STORM_HOME in the classpath
is for legacy purposes, meaning we missed changing it when we made the update.
If you want to file a JIRA and put up a pull request I would be happy to review
it and merge it in. AT a minimum please file a JIRA. - Bobby
On Monday, February 9, 2015 7:13 AM, 田杰 <[email protected]> wrote:
Suppose my Storm exists in /home/storm/storm-0.9.0.1:
By checking the script "bin/storm", I find it collects all jars in
"/home/storm/storm-0.9.0.1"(HOME_DIR) and "storm-0.9.0.1/lib/" into CLASSPATH
( ... -cp ...).
I just think it is a little tricky here to collect all jars under
storm-0.9.0.1/ (the HOME_DIR of Storm) into CLASSPATH by default.
If some guy uploaded his topology jar package into the HOME_DIR( by mistake),
and forgot to delete it, a new jar with the same name at anywhere else cannot
have chance to be submitted in future( Storm will always select the old jar in
the HOME_DIR firstly ).
I know it has little chance to hit, but it could bring trouble to Users if it
really happened. I just met this problem days ago( the "bad" jar was uploaded
by others)
Could we move the necessary jar packages into storm-0.9.0.1/lib or a new
directory, and not collect jars in the HOME_DIR by default?
It is just my suggestion and sorry if any mistake above.
Thanks.
Best Regards,
Alex Tian
