[
https://issues.apache.org/jira/browse/SOLR-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817519#comment-17817519
]
Jan Høydahl commented on SOLR-8680:
-----------------------------------
Now that solrj is being split in several parts, do you think it makes sense to
distribute an uber-jar "solrj-all" with the main purpose of satisfying needs of
JDBC users?
Should it ibe a "OneJar" style jar with all dependencies embedded, or simply a
mashup of solrj packages with the need to include the handful of external
dependencies?
If OneJar, should we shade all dependencies (non-solr pkgs) to avoid version
conflicts in users' applications? Such a shaded JAR will be quite fat and add
much weight to our release tarball. So perhaps consider a separate release
artifact for it?
> Distribute JDBC driver as a separate jar
> ----------------------------------------
>
> Key: SOLR-8680
> URL: https://issues.apache.org/jira/browse/SOLR-8680
> Project: Solr
> Issue Type: New Feature
> Components: Parallel SQL
> Reporter: Joel Bernstein
> Priority: Major
> Attachments: SOLR-8680.patch
>
>
> Currently the JDBC driver comes included with the Solrj libraries. As the
> JDBC driver matures it will be useful to distribute a separate jar which
> includes all of the dependancies, rather then having to include all the Solrj
> dependancies separately. This will make it much easier to install and ship
> with products like JasperSoft, Spotfire and Tableau.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
