Fix categorization for Moderne recipes

[mike-solomon]

Right now Moderne recipes are going into strange categories because we've named the recipes weirdly.

For example, our Spring Boot 3.4 recipe - https://docs.openrewrite.org/recipes/recipe/spring/boot3/upgradespringboot_3_4 has a recipe id of: io.moderne.recipe.spring.boot3.UpgradeSpringBoot_3_4 - which means that it's under the page: recipe -> spring -> boot3.

This is problematic as it should be Moderne -> Java -> Spring -> Boot3.

This applies to many recipes such as Hibernate. Similarly, https://docs.openrewrite.org/recipes/compiled/verification/changelistmethodandverify - this should have a category of compiled verification and not compiled -> verification.

We need to either rename all of the recipes to have the correct path - or we need to write code to map these recipe ids to categories.

Related thread: https://moderneinc.slack.com/archives/C01VADFPJQZ/p1739899709537709

[okundzich]

I think we just rename them to have this path Moderne -> Java -> Spring -> Boot3. it's just two modules and 10s of customers that we can communicate this to. I'm not sure what we did to advertise available recipes to them in the SaaS (new modules). I remember we discussed this. We would also need to delete the old jars.

In any case if we have such categories for Moderne proprietary recipes, than we can strip Moderne from the path and put them in the regular catalog under Moderne Proprietary heading

So this

becomes

Then we don't have to figure out how to link them across different trees. We just need to follow a convention that Moderne recipes need to have the same path hierarchy as OS ones, just with io.moderne not org.openrewrite.

[okundzich]

if we do this then issues #168 and #169 can be closed.

As a follow up, we also have some recipes with org.openrewrite path that are proprietary, and we know what license they have since we display it. This also can be sorted into Moderne Proprietary Categories/Recipes and Categories/Recipes.

Then we have a single category catalog that specifies recipes OSS and Moderne for different migrations/tasks.

[okundzich]

This is how it can look if paths are the same only prefix is different. It will help people see at a glance the benefits of moderne recipes.

[okundzich]

Also this category Recipes needs to be renamed. I think still ok to rename in path?

[timtebeek]

Linking this issue here as well as it might clear out some of the discrepancies between OSS docs & Moderne Platform:

• Adopt CategoryTree for determining Recipe categorization #3 (comment)

[kmccarp]

Can we just rename the recipes? Literally run change package name recipe on all these packages in the recipe jars? We're well within the timeframe to be able to rename them. I would rather do that than build something custom for this case.

[timtebeek]

We've now renamed the packages, but there's further work to do still:

• https://github.com/moderneinc/rewrite-hibernate/pull/5
• https://github.com/moderneinc/rewrite-spring/pull/27
• https://github.com/moderneinc/rewrite-ai-search/commit/76df9fb37d57791f0e86e9d5eb1f0b46878045f1

Waiting to hear if this might help, as I've not wrestled with our categories handling much before:

• Add io.moderne as root category, same as org.openrewrite rewrite#5067

[sambsnyd]

I merged the PR Tim had open to mark io.moderne as a root category. I believe that will help