Sebastian Schuberth

I haven't checked, but my hunch is that this happens because the monorepo contains both the source code to a package (which ORT treats as a project then), *and* another...

BTW, as of https://github.com/oss-review-toolkit/ort/pull/6241 you should actually also get a better error message in this case.

> Wouldn't it be possible to implement the same option for the analyze phase as a workaround, like not treating them? See https://github.com/oss-review-toolkit/ort/issues/5968 😉

> > Wouldn't it be possible to implement the same option for the analyze phase as a workaround, like not treating them? > > See #5968 😉 The PR has...

Note to myself: A comparison to https://github.com/seaweedfs/seaweedfs would be interesting.

Ping @seabass-labrax who told me at [PackagingCon](https://packaging-con.org/) that he'd be willing to help here.

> with some languages like Kotlin. Or switch to Kotlin for its null-safely and less boilerplate, targeting the JVM only first, but eventually opening the target audience to [multi-platform](https://kotlinlang.org/docs/multiplatform.html)?

FYI, this fork claims to have some RDFa 1.1 work done, in the same commit that upgrades to Jena 3.0.0: https://github.com/funkwill/java-rdfa/commit/0e3e10a548357fe3bd45bb7033636ab0ccea443f

Probably [Detekt](https://github.com/detekt/detekt) with [KtLint-based formatting rules](https://github.com/detekt/detekt#adding-more-rule-sets) enabled?

I just found [this discussion](https://github.com/Strumenta/antlr-kotlin/pull/111#discussion_r1417659168), but just as a remark, of course *KtLint* is way more Kotlin-specific style checks than `.editorconfig`, and via *Detekt* it's also not "a PITA" to...