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 01:07:15 UTC
[jira] [Updated] (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 updated SOLR-6339:
---------------------------
Description:
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?-
was:
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?
Assignee: Hoss Man
Summary: why does SolrXMLSerializer exist? (was: why does SolrXMLSerializer.fileCopy exist? replace with FileUtils.copyFile?)
> 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
>
> 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