[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223370#comment-13223370
]
Robert Muir commented on SOLR-3204:
-----------------------------------
{quote}
Well, I do see the problem with jetty but doubt the other dependencies are that
problematic.
{quote
Jarjaring is dangerous also because of reflection in from other libraries.
For example, if we find a bug in ICU, submit it, and they commit it, we should
be able to
depend upon a snapshot unreleased build of ICU, yet, at the same-time, arabic
PDF extraction
should still work (apache PDFBox reflects the icu package names to determine if
this works).
So renaming packages with jarjar is not safe for a number of reasons, I really
don't think
we should do this just to satisfy maven.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
