lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3204) solr-commons-csv must not use the org.apache.commons.csv package
Date Wed, 07 Mar 2012 20:42:58 GMT


Dawid Weiss commented on SOLR-3204:

bq. For carrot: If you can just compile carrot with Java 5 and produce Java 5 JARs, why does
Dawid/Carrot not do this? A Java 6 class/jar file is not really useful if just the version
number of the file header is different...

It's not that simple. We use 1.6 APIs and we have libraries that are compiled under 1.6. The
version embedded in Solr is patched and backported using retroweaver if I remember correctly.
Like I said, I don't have a problem if you just publish that particular artefact as is under
Solr's groupid. I don't see a problem here, really. Classpath conflicts do happen but it's
easier to recover from a classpath conflict than from a jarjared file which happens to use
runtime reflection or something like that (just replacing strings is often not enough if class
names are constructed dynamically).

> 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-3204.patch, SOLR-3204.patch, SOLR-3204.patch, apache-solr-commons-csv-1.0-SNAPSHOT-r966014.jar,
rule.txt, rule.txt, 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