[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223198#comment-13223198
]
Emmanuel Bourg commented on SOLR-3204:
--------------------------------------
I agree a release of Commons CSV is desirable, but that's not a reason for
using the namespace of other projects. The artifact is free to use by anyone
from the Maven repository, it's no longer an implementation detail of Solr,
people are starting to use it in the wild, and this will lead to classpath
conflicts.
Repackaging a Commons component and renaming its package isn't uncommon, Tomcat
does this for DBCP:
http://www.jarvana.com/jarvana/inspect/org/apache/tomcat/tomcat-dbcp/7.0.23/tomcat-dbcp-7.0.23.jar
Tomcat is released with a tomcat-dbcp artifact containing the DBCP classes but
under the org.apache.tomcat.dbcp package. Solr should adopt the same approach
until Commons CSV is officially released.
> solr-commons-csv must not use the org.apache.commons.csv package
> ----------------------------------------------------------------
>
> Key: SOLR-3204
> URL: https://issues.apache.org/jira/browse/SOLR-3204
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.5
> Reporter: Emmanuel Bourg
> Priority: Minor
> Fix For: 3.6
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
