[
https://issues.apache.org/jira/browse/LUCENENET-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shad Storhaug resolved LUCENENET-574.
-------------------------------------
Fix Version/s: Lucene.Net 4.8.0
Assignee: Shad Storhaug
Resolution: Fixed
Fixed in https://github.com/apache/lucenenet/pull/567
> [Serializable] Classes
> ----------------------
>
> Key: LUCENENET-574
> URL: https://issues.apache.org/jira/browse/LUCENENET-574
> Project: Lucene.Net
> Issue Type: Improvement
> Affects Versions: Lucene.Net 4.8.0
> Reporter: Shad Storhaug
> Assignee: Shad Storhaug
> Priority: Minor
> Labels: up-for-grabs
> Fix For: Lucene.Net 4.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Lucene.Net 3.0.3 several classes were marked with the [Serializable]
> attribute. The same has been done to several of the classes in the Lucene.Net
> (core), but most of the classes in the sub-projects are still not
> serializable.
> Some of the legacy tests that were carried over required certain classes to
> be serializable (LUCENENET-170 and LUCENENET-338), which is how this issue
> was first discovered.
> At the very least, all Queries, Filters, and Analyzers should be marked
> [Serializable], but it is unclear what criteria version 3.0.3 used to
> determine which other classes should be serializable. We need a clear
> strategy for this as well as the task to be done.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
