[
https://issues.apache.org/jira/browse/SOLR-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242374#comment-13242374
]
Dawid Weiss commented on SOLR-3296:
-----------------------------------
I guess this means "official apache releases" but if the release is done in a
private namespace then this isn't a problem? I mean -- I could probably take
the source right now, change the group id to something I have access to
(com.carrotsearch.thirdparty) and release it, but so can Yonik (under his own
domain or whatever namespace he wishes that is different than Apache's)?
I admit this is kind of weird that Solr is using something that cannot be
officially released. Why not make it part of Solr then? Just copy the source
code over and publish as a separate artefact?
> Explore alternatives to Commons CSV
> -----------------------------------
>
> Key: SOLR-3296
> URL: https://issues.apache.org/jira/browse/SOLR-3296
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Reporter: Chris Male
>
> In LUCENE-3930 we're implementing some less than ideal solutions to make
> available the unreleased version of commons-csv. We could remove these
> solutions if we didn't rely on this lib. So I think we should explore
> alternatives.
> I think [opencsv|http://opencsv.sourceforge.net/] is an alternative to
> consider, I've used it in many commercial projects. Bizarrely Commons-CSV's
> website says that Opencsv uses a BSD license, but this isn't the case,
> OpenCSV uses ASL2.
--
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
