lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3204) solr-commons-csv must not use the org.apache.commons.csv package
Date Tue, 06 Mar 2012 17:34:58 GMT


Emmanuel Bourg commented on SOLR-3204:

Torsten, in case you're wondering why nobody is answering you: Lucene/Solr publishes Maven
artifacts that are identical to the released Ant-built binary jars, so your proposal would
require increasing the size of our released jars, solely to solve a Maven dependency problem.
Changing the Ant build simply to solve Maven problems has historically been a non-starter.
Steven, this will not increase the global size of the distribution, it might even reduce it.
You are trading a core Solr jar with a few modified dependent jars, all downloaded from the
central Maven repository, for a unique jar containing Solr and it dependencies, and possibly
only the necessary classes. For example Solr doesn't use the writer package of Commons CSV,
it can be automatically removed in the process to reduce the size of the dependencies.

Still not interested? :)
> solr-commons-csv must not use the org.apache.commons.csv package
> ----------------------------------------------------------------
>                 Key: SOLR-3204
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.5
>            Reporter: Emmanuel Bourg
>            Priority: Blocker
>             Fix For: 3.6
>         Attachments: solr-csv.patch
> The solr-commons-csv artifact reused the code from the Apache Commons CSV project but
the package wasn't changed to something else than org.apache.commons.csv in the process. This
creates a compatibility issue as the Apache Commons team works toward an official release
of Commons CSV. It prevents Commons CSV from using its own org.apache.commons.csv package,
or forces the renaming of all the classes to avoid a classpath conflict.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message