Skip to content

Fixed used JavaParser when adding JavaSources #419

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

Conversation

fabapp2
Copy link
Contributor

@fabapp2 fabapp2 commented Sep 19, 2022

closes #418

@fabapp2 fabapp2 force-pushed the 418-after-applying-initialize-spring-boot-migration-the-recipe-is-still-shown-as-applicable branch from 3b2f709 to 0da1454 Compare September 19, 2022 18:33
@fabapp2 fabapp2 changed the title Fixing parser usage Fixing parser usage when adding JavaSources Sep 19, 2022
@fabapp2 fabapp2 merged commit 253f337 into main Sep 19, 2022
@fabapp2 fabapp2 deleted the 418-after-applying-initialize-spring-boot-migration-the-recipe-is-still-shown-as-applicable branch September 19, 2022 18:56
@fabapp2 fabapp2 changed the title Fixing parser usage when adding JavaSources Fixed used JavaParser when adding JavaSources Sep 23, 2022
@fabapp2 fabapp2 self-assigned this Sep 23, 2022
@fabapp2 fabapp2 added the type: enhancement New feature or request label Sep 23, 2022
@fabapp2 fabapp2 added this to the v0.12.0 milestone Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

After applying initialize-spring-boot-migration the recipe is still shown as applicable
1 participant