Sebastian Schuberth

Looks like this should be aligned with the Maven 4.0.0 release.

> Drop support for all _ScanCode_ versions prior to 30.1.0 from _ORT_, to simplify the code. More generally, we should say "drop support for all ScanCode versions that do not...

> So, I wanted to save the effort to investigate that old 30.0.0 support. I believe we can skip it anyway, as like we discussed, with general `outputFormatVersion` support the...

Maybe we should work on this issue before upgrading to [ScanCode 32.3.0](https://github.com/aboutcode-org/scancode-toolkit/releases/tag/v32.3.0), which introduces new major output format version 4.0.0.

This probably requires to change `WorkingTree.listRemoteTags()` to return `Map` instead of `List` to get the revisions for the tag names as well, in order to "deduplicate" tag names by revision.

@maxhbr is this something you could help with? Is there maybe even a JSON schema for Opossum that we could generate Kotlin code from?

> Hey, I posted it in our group chat. Were there any responses @maxhbr?

> > Hey, I posted it in our group chat. > > Were there any responses [@maxhbr](https://github.com/maxhbr)? @maxhbr is the Opossum reporter still in use from your side? Otherwise we...

> Yeah, we are difinitely still using it. Thanks @leslielazzarino for the comment. Is there also willingness to help maintaining it from your side, and assist with the migration to...

> Hi [@sschuberth](https://github.com/sschuberth) I am taking a look. Thank you @alexzurbonsen 🙏🏻 Ideally, the conversion would not be done by simply migrating those untyped maps to KxS equivalents, but by...