[
https://issues.apache.org/jira/browse/LUCENE-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307950#comment-17307950
]
Dawid Weiss commented on LUCENE-9863:
-------------------------------------
bq. I just feel guilty "throwing a lot of issues over the fence" versus trying
to fix them myself.
No worries.
bq. So I was trying to brainstorm ways of making the code more accessible.
This is a problem with gradle in general - it's not an easy build system
(groovy, APIs, conventions, gotchas with
inputs/ outputs, etc.)... I tried to make it less noisy by splitting the build
into smaller aspect-like pieces but even this may be hard to grasp for a
newcomer ("How come the configuration of my task can be scattered across
multiple files?!").
I don't have an answer to this. Cedric Beust had a similar system in Kotlin but
that never took off, it seems (https://github.com/cbeust/kobalt).
> run spotless across groovy (e.g. gradle) code too
> -------------------------------------------------
>
> Key: LUCENE-9863
> URL: https://issues.apache.org/jira/browse/LUCENE-9863
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
>
> We should run spotless to format the groovy, too so that there is a
> consistent style and nobody needs to think about how the formatting should be.
> Especially considering how crazy the language is, it is even more important
> to do this than with the java!
--
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
