Lombok and spring-boot-configuration-processor are ordered contrary to Boot's docs

[wilkinsona]

Boot's docs instruct users to configure their project's annotations processor so that Lombok runs before spring-boot-configuration-processor:

If you are using Lombok in your project, you need to make sure that its annotation processor runs before spring-boot-configuration-processor. To do so with Maven, list the annotation processors in the required order using the annotationProcessors attribute of the Maven compiler plugin. With Gradle, declare the dependencies in the annotationProcessor configuration in the required order.

start.spring.io does not do this for either Maven or Gradle with, as far as I can tell, the generated configuration always resulting in Lombok running second. See spring-projects/spring-boot#50121 for an example of a problem that this can cause.

[sri1873]

Hey, I looked into this, and currently the initializr generates annotations processor in ConvertAnnotationProcessorsToPluginConfigBuildCustomizer.java (for Maven) by iterating over a set of dependencies

Set<String> ids = build.dependencies().ids().collect(Collectors.toSet());

So, no order is being followed, I think setting a priority to each dependency would be overkill. A simpler workaround could be to always add spring-boot-configuration-processor last (if present), allowing the project's other annotation processors to run first.

If this aligns with what you had in mind , I'd be happy to work on this issue and open a PR.

Also, since the relevant code is in the Initializr repository rather than start.spring.io, I think this issue should probably be moved there.