You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2014/08/08 02:15:11 UTC
[jira] [Resolved] (SOLR-6339) why does SolrXMLSerializer exist?
[ https://issues.apache.org/jira/browse/SOLR-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-6339.
----------------------------
Resolution: Fixed
Fix Version/s: 4.10
5.0
nuked it ... forgot to site jira in the commit message...
Committed revision 1616646.
Committed revision 1616648.
> why does SolrXMLSerializer exist?
> ----------------------------------
>
> Key: SOLR-6339
> URL: https://issues.apache.org/jira/browse/SOLR-6339
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 5.0, 4.10
>
>
> Scratch that ... this entire class appears to be dead code that can be ripped out.
> -a question on the mailing list about SolrXMLSerializer.fileCopy drew my attention to this method, and has me wondering why it needs to exist at all?-
> -couldn't we just rip this out and replace it with a call to FileUtils.copyField from commons-io?-
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org