Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample scaffolding for Spring Framework migrations #157

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jmle
Copy link
Contributor

@jmle jmle commented Oct 4, 2024

Scaffolding example for rules for the migration path from Spring Framework 5.x to 6.0. Issues have been created with the spring-migration/6.0 tag: spring-migration/6 Label for Spring Migration path 5 -> 6 .

The idea is to have rules separated by modules so that they can be easily worked with. Tests could either be placed on the root of the target technology or inside a tests folder (the second option has been chosen in this case).

spring-framework
├── ruleset.yaml
├── spring-framework-5.x-to-6.0-core-container.yaml
├── spring-framework-5.x-to-6.0-removed-apis.yaml
└── tests
    ├── spring-framework-5.x-to-6.0-core-container.test.yaml
    ├── spring-framework-5.x-to-6.0-removed-apis.test.yaml
    └── test-data
        ├── spring-framework-5.x-to-6.0-core-container
        └── spring-framework-5.x-to-6.0-removed-apis

Signed-off-by: Juan Manuel Leflet Estrada <[email protected]>
Signed-off-by: Juan Manuel Leflet Estrada <[email protected]>
@jmle jmle added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant