lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (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:17:58 GMT


Ralph Goers commented on SOLR-3204:

Robert, if you are not releasing code then how did the artifact find its way into the Maven
Central repository? The maintainers of the repository will ONLY accept artifacts when they
come from the appropriate place - in this case that would need to be Apache's repository.
I can't imagine how anyone other than Solr's team could have caused that to happen.

As for snapshots, that doesn't really solve the problem as you can't release with a dependency
on a snapshot.

If the intent was just to use the jar internally in a war file that your customers don't change
then somewhere in your build you have a mistake as the jar is apparently being made available
to the public. If, however, the dependency is required for users or Solr to do builds then
you need to change the package names so that they don't conflict with those in Commons.
> 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