Hello devs, we have lots of package name conflicts (shared package names) between modules in the Lucene/Solr source tree. It is not only annoying for devs/users but also indeed bad practice since Java 9 (according to my understanding), and we already have some problems with Javadocs due to these splitted packages as some of us would know. I'm curious about the issue from a while ago. My questions are, Q1: How can we solve the issue in an organized way? Q2: How many of us really have interests about that?
To break down Q1, - A JIRA for building a grand design and organizing sub tasks is needed? We have a couple of issues (e.g. LUCENE-9317 and LUCENE-9319) about it and I had been playing around them before; but I feel like an umbrella ticket would be needed. - When to start and what's the target version to be out? My feeling is that after cutting branch_9x is the right moment to start and 10.0.0 is suitable for the target, does this make sense? - Are there any other tasks/concerns to be considered except for just renaming packages? Regarding Q2, I know some of us have deep knowledge and thoughts in this topic, but for now I am not sure how many of you have the will to give help or take time for that. It can't be a one-man effort. The more people understand and can contribute to the build, the more healthy it will be. (I borrowed this phrase from Gradle build issue LUCENE-9077). I don't intend to rush into making a decision, my purpose here is to collect information to see if I can handle it before opening a JIRA. Thanks, Tomoko
