Epic: Extract OpenRewrite parser

[fabapp2]

What needs to be done

The parsing logic to create the OpenRewrite AST from given resources should be extracted.
The currently used MavenProjectParser should then be replaced by this component.

Why it needs to be done

Parsing a given project to OpenRewrite AST is a mandatory step to apply OpenRewrite recipes.
Currently, two open-sourced build tool plugins exist that allow applying recipes inside a build.
Providing a parser that creates the AST outside of a build tool plugin is required for other projects too.
Extracting the parser allows reusing this component in these projects.

• feat: Add project parser for OpenRewrite #832
  • Adhere to .mvn/maven.config (MavenConfigFileParserTest)
  • Adhere to ~/.m2/settings-security.xml and ~/.m2/settings.xml #880
  • Publish parsing events registered through the ExecutionContext as Spring application events #892
• Make PomCache configurable through properties #855
• Parse Gradle projects #849
• Make MavenArtifactCache configurable #856
• All markers should be added exactly as if the project would have been parsed with the build tool plugins
• The ExecutionContext should be made available as scoped bean, reusing Reusable Execution Context #792 and 786 reusable execution context 2 #800
• All Java versions supported by OpenRewrite must be supported (SBM tool - migrate-stateless-ejb isssue #837)
• The component should be configurable through Spring properties
  • A rewrite.yaml should read and the settings should be taken
• Exception handling should be configurable
  • When to throw and when to log
  • how to communicate exceptions (print in resource, collect, ...)
• Build information (ordered list of build files, dependencies for modules, and other) can be provided
• Parser should apply to OpenRewrite styles #982
• Allow different pom and artifact caches
• Ignore all resources in .gitignore when scanning #78
• Provide a common interface and make parser implementation configurable (RewriteMavenProjectParser vs. RewriteProjectParser)
• Support Maven profiles(?)
• Add tests
  • Test that dependencies are downloaded when local repo is empty
  • Integration tests using local artifact repository (e.g. Artfactory) with credentials to retrieve dependencies
  • Add parity check for parent.modules in MavenResolutionResults in ParserParityTestHelper #991

Acceptance Criteria

/info panel
Given precondition
When action
Then result

Additional Information

[shresthaujjwal]

@fabapp2 any idea when the support for custom maven settings.xml support would be added ? Adhere to ~/.m2/settings-security.xml and ~/.m2/settings.xml

[fabapp2]

Hi @shresthaujjwal

it should be working with the current parser used in isolation when using RewriteMavenProjectParser which replicates works as with the rewrite-maven-plugin.
It needs to be incorporated into the RewriteProjectParser and can be taken fron here. I will find or create an issue for this.