[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223829#comment-13223829
]
Steven Rowe commented on SOLR-3204:
-----------------------------------
bq. I'm glad to hear you are willing to do something, what's your plan?
I don't have one yet. What's your plan for releasing commons-csv?
{quote}
Let me recap the options currently identified:
1. Embed the Commons CSV source files in the core of Solr. That was the purpose
of my patch, but it doesn't solve the issue for the other dependencies (carrot,
noggit, uima, jsonic, etc)
{quote}
-1. I think this is too intrusive. Maven's requirement cannot dictate
Lucene/Solr Ant build structure.
bq. 2. Embed the pacthed dependencies in the main Solr jar and rename the
packages with jarjar or a similar tool. The additional benefit it a reduction
of the global distribution size by keeping only the classes actually used by
Solr.
-1. Again, too intrusive.
bq. 3. Keep publishing Solr specific dependencies but after renaming the
packages with JarJar
I think this is a possibility.
bq. 4. Import the source of the dependencies and rename the package with the
Ant replace task (Tomcat solution)
-0. The project would require a new module for each dependency. Seems too
heavy to me.
bq. 5. Stop releasing Maven artifacts completely, even Solr core.
;) Fantastic! Thanks for your input! You're, like, awesome!
> 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
> Components: Build
> Affects Versions: 3.5
> Reporter: Emmanuel Bourg
> Priority: Blocker
> Fix For: 3.6
>
> Attachments: SOLR-3204.patch, 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:
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
