[LUCENE-9319] Clean up Sandbox project by retiring/delete functionality or move it to Lucene core

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: master (9.0)
• Fix Version/s: master (9.0)
• Component/s: core/other
• Labels: build features
• Lucene Fields: New
• Assignee: Tomoko Uchida
• Reporter: David Ryan
• Created: 12/Apr/20 04:24
• Updated: 05/Nov/20 06:06
• Resolved: 05/Nov/20 06:06

Description

To allow Lucene to be modularised with Java module system there are a few preparatory tasks to be completed prior to this being possible. These are detailed by Uwe on the mailing list here:

http://mail-archives.apache.org/mod_mbox/lucene-dev/202004.mbox/%3c0a5e01d60ff2$563f9c80$02bed580$@thetaphi.de%3e

 

The lucene-sandbox currently shares package names with lucene-core which is not allowed in the Java module system.  There are two ways to deal with this. Either prefix all packages with "sandbox" or retire the lucene-sandbox all together. As per the email:

Cleanup sandbox to prefix all classes there with “sandbox” package and where needed remove package-private access. If it’s needed for internal access, WTF: Just move the stuff to core! We have a new version 9.0, so either retire/delete Sandbox stuff or make it part of Lucene core.

 The suggested way forward is to move sandbox code to core.

 

Issue Links

• is a child of: LUCENE-9499 Clean up package name conflicts between modules (split packages)
• links to: GitHub Pull Request #2023