Dawid Weiss created LUCENE-10324:
------------------------------------
Summary: Automatic cross-validation between the graph of modules
and declared dependencies in gradle
Key: LUCENE-10324
URL: https://issues.apache.org/jira/browse/LUCENE-10324
Project: Lucene - Core
Issue Type: Sub-task
Reporter: Dawid Weiss
I'm not sure it's possible for these to go out of sync without the compilation
breaking but perhaps there is an elegant way to verify 1:1 the consistency of
gradle configuration declarations and the module's actual content.
I believe the simplest way would be to collect metadata about the
configurations we know on the gradle side during compilation (moduleApi,
moduleImplementation...) - then we can read such metadata in, say, distribution
tests and verify if it's consistent with the module's declaration. This
metadata can even be embedded inside the module itself
(META-INF/gradle/metadata.properties or inside the manifest, as a separate
section).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
