[
https://issues.apache.org/jira/browse/LUCENE-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183299#comment-17183299
]
Uwe Schindler commented on LUCENE-9474:
---------------------------------------
bq. Gradle doesn't work like this. When you issue a command "./gradlew
assemble" it runs this task in any sub project that has such a task. There is
no need to add any dependencies. And the "root" project will be gone after the
split anyway - please don't add such synthetic dependencies.
I know why you want to split solr and lucene: Because of the project structure
it still feels like 2 projects. The problem is that Gradle can't handle that
correctly, because the uber ":lucene" project has no useful tasks, unless we
add them synthetically. All the magic of Gradle only works from root project.
I just asked to maybe add some "convenience tasks" to get people started, we
can remove them later - would also make my life as CI maintainer easier.
BTW, Elasticsearch is quite nice. When you run "gradlew assemble", you get the
ZIP file also in a packaging subproject!
> Change Jenkins jobs to use Gradle for trunk
> -------------------------------------------
>
> Key: LUCENE-9474
> URL: https://issues.apache.org/jira/browse/LUCENE-9474
> Project: Lucene - Core
> Issue Type: Test
> Components: general/build
> Reporter: Erick Erickson
> Assignee: Uwe Schindler
> Priority: Major
>
> I rushed the gate and pushed LUCENE-9433 without coordinating, my apologies
> for the confusion.
> Meanwhile, Uwe has disabled Jenkins jobs for the weekend and we'll fix this
> up Real Soon Now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
