Polyglot for Maven VS Design Patterns

And you don't even need to use XML with Polyglot Maven

https://github.com/takari/polyglot-maven

If you prefer the shorter alternative, you might want to use the Polyglot XML extension https://github.com/takari/polyglot-maven/tree/master/polyglot-xml

Here you go: https://github.com/takari/polyglot-maven

Fun fact, POM files can be in formats other than XML (although I have no idea if IJ would tolerate such shenanigans): https://github.com/takari/polyglot-maven/blob/polyglot-0.4.8/polyglot-yaml/src/test/resources/snakeyaml/pom.yaml

There is a certain argument to be made for user ergonomy. Many developers are drawn to Gradle and friends, or to work with polyglot Maven, because they support a more concise syntax. This is not necessarily a contradiction with Maven's Goals!

I wished they‘d finally embrace polyglot maven https://github.com/takari/polyglot-maven. pom.yaml rule the world.

It seems merely adding a file to the .mvn directory will do as you wish: https://github.com/takari/polyglot-maven#usage

I have avoided that road because it's one more thing that is a snowflake in the very area where I don't want to blazing trails. But I have personally tried their approach before and can confirm it does work as advertised. I can't recall if IJ lost its mind over pulling a stunt like that, but arguably if it did, then filing a YouTrack is an appropriate next step

After that, more practice, and then Design Patterns (as in the famous book of the "Gang of Four": "Design Patterns: Elements of Reusable Object Oriented Software"). Here I'd recommend "Head First: Design Patterns" and Java Design Patterns as well as Refactoring Guru (the sites are more reference than course).

For Design Patterns - any resource recommendation that misses Java Design Patterns and Refactoring Guru (also for Refactoring) as well as *Head First: Design Patterns, has failed.

A massive list of design patterns and how they could be implemented (in Java) can be found here.

https://java-design-patterns.com/ has example code for things like object pools that can help with memory management.

Sidenote: I would not really use the GoF Design Patterns book anymore. Too dry. I would use "Head First: Design Patterns" - much more modern, much easier to read, or Refactoring Guru or Java Design Patterns (uses Java, but again, only for illustrations).

Also: https://java-design-patterns.com and https://refactoring.guru/design-patterns

Use either Java Design Patterns or Refactoring Guru. Both resources are far higher quality than yours.

Java Design Patterns

Java Design Patterns - IMO one of the most accessible sites with very easy explanations

A hint: go to Java Design Patterns and go through the patterns to figure what could fit.