You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RewriteProjectParser in sbm-support-rewrite starts Maven to provide the input data for OpenRewrite's Maven plugin code. It should be refactored to not require Maven.
Why it needs to be done
Starting the Plexus container from within a Spring application fails because the Plexus container does not find all components and can't start up. This only happens in Spring Boot applications indicating a conflict when loading jars from BOOT-INF/libs.
When using Maven to parse the poms, the project must always be a valid Maven project and thus every recipe must leave the application in a buildable state. Otherwise the migration will be stuck and running other recipes is not possible.
The parser uses Maven classes and is therefore coupled to java.io.File requiring the resources to exist on the filesystem. Previously Springs Resource abstraction was used which allowed "synthetic" dummy resources that didn't need to exist on FS. Removing the need for Maven would allow using Resources again.
Acceptance Criteria
/info panel Given precondition When action Then result
Additional Information
The text was updated successfully, but these errors were encountered:
What needs to be done
The
RewriteProjectParser
insbm-support-rewrite
starts Maven to provide the input data for OpenRewrite's Maven plugin code. It should be refactored to not require Maven.Why it needs to be done
java.io.File
requiring the resources to exist on the filesystem. Previously SpringsResource
abstraction was used which allowed "synthetic" dummy resources that didn't need to exist on FS. Removing the need for Maven would allow usingResource
s again.Acceptance Criteria
/info panel
Given precondition
When action
Then result
Additional Information
The text was updated successfully, but these errors were encountered: