[
https://issues.apache.org/jira/browse/LUCENE-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183296#comment-17183296
]
Uwe Schindler commented on LUCENE-9474:
---------------------------------------
Hi Dawid,
bq. My experience tells me that it really is more convenient to have a
dedicated sub-project for assembling everything into a distribution package.
Such a "packaging" project has benefits – everything related to packaging is
there, any "distribution" tests can simply depend on it and consume its
artifacts (ZIP with the distribution). Look at the Solr 'packaging' project and
you'll see what I mean.
Fully agree. I had that in mind, but did not find "how to do this". Basically
we have jenkins jobs to build just the release artifacts. I would like to get
the command lines / tasks how to assemble that. For Solr, I know now. So for
solr I can build documentation and package using:
{code}
$ gradlew :solr:packaging:assemble :solr:documentation
{code}
For Lucene, I will remove the first task invokation until the package assembly
subproject is done. So I can publish at least the Javadocs like before.
> 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
