[
https://issues.apache.org/jira/browse/LUCENE-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081672#comment-17081672
]
Tomoko Uchida commented on LUCENE-9317:
---------------------------------------
[~oobles] I just came here from the mail list. I just wanted to leave my
comments / suggestions for your question.
{quote}
I've checked out the master branch and starting to look at setting up the
development environment using Gradle to see if I can assist with a few items. I
notice Gradle hasn't been set up for Eclipse yet (maybe something I can help
with).
{quote}
Did you try "ant eclipse"? While Gradle build is already in a good shape, it is
ongoing project for now. Still we use Ant build as our first class build system
and it will help you when you see Gradle tasks doesn't work for you.
{quote}
My first roadblock to getting setup is understanding the cyclic dependencies
between core, codecs and the test-framework. Given IRC is not really used from
what I can see, and the slack channel is private to people with @apache.org
emails. Is there any good place to get basic help on getting started with the
codebase without spamming this email list?
{quote}
We are using Jira or Github PR as a general communication tool for specific
issues (discussion about design or implementation, questions, review requests,
or everything else). You can also get basic help here. I suggest you read the
contribution guide if you have not done so already:
https://cwiki.apache.org/confluence/display/solr/HowToContribute
I have a bit experience of analysis framework and I'm also sometimes annoyed
with its split package issue. Please feel free to mention me if you feel you
need "basic help" here.
> Resolve package name conflicts for StandardAnalyzer to allow Java module
> system support
> ---------------------------------------------------------------------------------------
>
> Key: LUCENE-9317
> URL: https://issues.apache.org/jira/browse/LUCENE-9317
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/other
> Affects Versions: master (9.0)
> Reporter: David Ryan
> Priority: Major
> Labels: build, features
>
>
> To allow Lucene to be modularised there are a few preparatory tasks to be
> completed prior to this being possible. The Java module system requires that
> jars do not use the same package name in different jars. The lucene-core and
> lucene-analyzers-common both share the package
> org.apache.lucene.analysis.standard.
> Possible resolutions to this issue are discussed by Uwe on the mailing list
> here:
>
> [http://mail-archives.apache.org/mod_mbox/lucene-dev/202004.mbox/%3CCAM21Rt8FHOq_JeUSELhsQJH0uN0eKBgduBQX4fQKxbs49TLqzA%40mail.gmail.com%3E]????
> {quote}About StandardAnalyzer: Unfortunately I aggressively complained a
> while back when Mike McCandless wanted to move standard analyzer out of the
> analysis package into core (“for convenience”). This was a bad step, and IMHO
> we should revert that or completely rename the packages and everything. The
> problem here is: As the analysis services are only part of lucene-analyzers,
> we had to leave the factory classes there, but move the implementation
> classes in core. The package has to be the same. The only way around that is
> to move the analysis factory framework also to core (I would not be against
> that). This would include all factory base classes and the service loading
> stuff. Then we can move standard analyzer and some of the filters/tokenizers
> including their factories to core an that problem would be solved.
> {quote}
> There are two options here, either move factory framework into core or revert
> StandardAnalyzer back to lucene-analyzers. In the email, the solution lands
> on reverting back as per the task list:
> {quote}Add some preparatory issues to cleanup class hierarchy: Move Analysis
> SPI to core / remove StandardAnalyzer and related classes out of core back to
> anaysis
> {quote}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
