You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2020/10/09 09:57:00 UTC
[jira] [Commented] (LUCENE-9562) Unify 'analysis' package with
produced artifact names
[ https://issues.apache.org/jira/browse/LUCENE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210781#comment-17210781 ]
Dawid Weiss commented on LUCENE-9562:
-------------------------------------
I filed a PR for this. All checks pass for me.
> Unify 'analysis' package with produced artifact names
> -----------------------------------------------------
>
> Key: LUCENE-9562
> URL: https://issues.apache.org/jira/browse/LUCENE-9562
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Lucene has 'analysis' module but its sub-modules produce 'lucene-analyzers-*' artifacts. This inconsistency is currently handled by setting artifact names manually:
> {code}
> configure(subprojects.findAll { it.path.contains(':lucene:analysis:') }) {
> project.archivesBaseName = project.archivesBaseName.replace("-analysis-", "-analyzers-")
> }
> {code}
> but I keep wondering if we should just make it one or the other - either rename 'analysis' to 'analyzers' or produce 'lucene-analysis-' artifacts.
> My personal opinion is to produce 'lucene-analysis-' packages because this keeps repository structure the same (backports will be easier) and we're targeting a major release anyway so people can adjust dependency names when upgrading. This change would be also consistent with package naming inside those modules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org