[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223440#comment-13223440
]
Steven Rowe commented on SOLR-3204:
-----------------------------------
bq. Uwe, no need to even publish those bugfix jars. I would just inline them
into the Solr artifact. (Think ueberjar) Then you don't even have to change a
line of java source code nor the bugfix jars. Just the build.
Torsten, in case you're wondering why nobody is answering you: Lucene/Solr
publishes Maven artifacts that are identical to the released Ant-built binary
jars, so your proposal would require increasing the size of our released jars,
solely to solve a Maven dependency problem. Changing the Ant build simply to
solve Maven problems has historically been a non-starter.
> 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]
