[
https://issues.apache.org/jira/browse/STORM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124989#comment-14124989
]
Naga Vijayapuram commented on STORM-483:
----------------------------------------
I propose this design -
. build/control the classpath internally within code for all the essential jars
that are part and parcel of storm
. designated dir(s) for worker, and for external (contrib and/or 3rd party
integration)
. an optional jars listing file within the dir(s) for orderly sequencing of the
jars in building the classpath further by appending jars to classpath
. within code - check if the jars listing file is present
. if present, read it to append jars to the classpath
. if not present, then get a listing of the jars present in the dir(s), and
append them to the classpath following natural ordering resulting from the
listing
> extlib for external (contrib and/or 3rd party integration)
> ----------------------------------------------------------
>
> Key: STORM-483
> URL: https://issues.apache.org/jira/browse/STORM-483
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Reporter: Naga Vijayapuram
> Priority: Minor
> Fix For: 0.9.3-incubating
>
>
> Proposing a dir (extlib) to hold jars for external (contrib and/or 3rd party
> integration). storm script can first pick up the jars in lib dir for
> classpath, and then the jars in extlib dir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
