[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224465#comment-13224465
]
Robert Muir commented on SOLR-3204:
-----------------------------------
Uwe: maybe we should do it just for this case (rather than offering a general
solution?)
Basically what i'm trying to say is that the general problem is complex, I
think there are enough examples (jetty, carrot2, uima, etc)
that fall in this category that aren't really solved by jarjar. I think we
either need to solve this issue as a 'case-by-case' for commons-csv,
or fix the entire problem (which definitely, definitely, certainly, without a
doubt, involves fixing maven).
But to be practical, lets come up with something so that commons-csv developers
are happy and can issue a release (which we can then depend upon).
Keeping in mind that this is supposed to be a 3.6 minor release, can we apply
the jarjar solution *only* to commons-csv?
I feel the other situations are more dangerous and I think we should be
careful, but at the same time we should address
their concerns and put ourselves in a situation where we don't end out
'forking' it... I don't want to see that.
> 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
