Rough draft of configuring the plugin based on the Maven plugin configuration

[nrayburn-tech]

Ref #107.

This is far from complete, but before I did much else with it I wanted to check that it's something the project would be interested in having added.

The way this works is that when you click the Maven sync action within IntelliJ, the Maven plugin configuration is read and synced with the IntelliJ plugin configuration.

Any code pointers are appreciated, but this is a really rough draft at this point and probably not worth spending much time reviewing the actual code.

[deepsource-io]

Here's the code health analysis summary for commits 8c610f8..d048dd6. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Java	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[jshiell]

Ooo, interesting. There's definitely demand for this, and the implementation seems nice & contained. It's definitely something I'd be open to adding as long as it's covered by test cases.

Thank you!

[nrayburn-tech]

I think this is roughly feature complete, with the exception of it not having any tests.

I wonder if this should wait until any Checkstyle version can be configured (ideally an outcome of #672). Otherwise, if the Maven project has a Checkstyle version specified that isn't supported then it will fallback to the IntelliJ plugin default.

An alternative to this would be if the Maven project has 10.1.2 configured and the known compatible version is 10.4.5, then we could set the configuration to use 10.4.5 directly.

---

Testing IntelliJ plugins is not something I've got much experience with, so it'll probably take a while for me to get suitable testing in place.

[nrayburn-tech]

Hopefully this goes without saying, but please let me know if there's any suggested changes that should be made.

For example, I know using var can be a preference so I don't mind changing it to explicit types. There might also be a better way for users to opt-in to the Maven import functionality. Maybe something to keep in mind is that this should be doable with Gradle as well, although I haven't explored that at all.