🐛 Bug Report: CatalogAnalysisExtensionPoint accepts only ScmLocationAnalyzer about backstage HOT 2 CLOSED

This sounds like one of those cases where we want the catalog extension point to have a cleaner interface than the underlying old stuff.

The extension point could have only a single setLocationAnalyzer that can be called only once. Then there can be a class DefaultLocationAnalyzer or something like that, that adopters can use if they want to tweak things. THAT class can have methods for adding additional sub-analyzer things in it if that's a pattern that's needed.

In all honesty, taking this even further, it could actually be argued that location analysis might have benefited from being an entirely separate plugin. But let's not go quite that far here. :) Just mentioning for context

from backstage.

Fix for this over in #24598

from backstage.