lucene-dev mailing list archives

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


Robert Muir commented on SOLR-3204:

Ralph: see Uwe's comment.

Its frequently the case that lucene/solr depend on things that are not in maven. When this
is the case, the guys who work on maven here
do whatever is necessary to make maven work (I really don't know the details, most of us just
use ant).

This is purely a maven issue, and as mentioned earlier, maven is provided as a convenience
for build configuration, no different from
convenience build configurations provided for Eclipse or Intellij IDEA.

Thats why I said: we aren't releasing anything. there is just commons-csv-1.0-SNAPSHOT-r966014.jar
in our solr/lib. Our ant build system
packages this up into solr.war

As for maven, eclipse, intellij, netbeans, whatever, it doesnt really matter to me how they
work, but supporting those alternative
build configurations != releasing code.
> 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