[
https://issues.apache.org/jira/browse/STORM-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209095#comment-15209095
]
ASF GitHub Bot commented on STORM-1625:
---------------------------------------
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1239#issuecomment-200529436
I'm +1 for merging this. I think moving the jars out of the lib folder is
the most important part for the 1.0 release. How to package the SQL
dependencies for the best user experience can be addressed in a follow-up JIRA
or as simple documentation instructing users what jars need to go where.
> Move storm-sql dependencies out of lib folder
> ---------------------------------------------
>
> Key: STORM-1625
> URL: https://issues.apache.org/jira/browse/STORM-1625
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core, storm-sql
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
>
> We shade guava classes inside storm-core so that client can work with any
> version of guava without any clashes. However, storm-sql-core has a
> transitive dependency on guava and thus the guava jar is still getting
> shipped in lib folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
