-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add update hint - recipes are not found any more when updating from 5.40.6 to 6.0.0 #203
Comments
Update: I get following output:
Which I didn't get at 5.40.6. I disabled all logging checks, the error of not found recipes persists. |
Hi @koppor ; we're still working on our 8.0 release, and as a part of that have released some components already, but have not yet completed the full release, and as a result of that have not updated the documentation yet either. Once we have fully released 8.0, there will be updated documentation and resources on how to upgrade, including some automated migration recipes. In your specific case the associated recipes have been moved to a separate repository: Just know that things are slightly in flux while we're working through this release; we hope to stabilize & document all of this quickly! |
Thank you for the quick answer. Seems, I need to be patient. A simple update of the recipes's names did not help
The
Ah, I need to use
OK, I am giving up and waiting for a full release. |
One more:
also does not help Link to mvnrepository: https://mvnrepository.com/artifact/org.openrewrite.recipe/rewrite-recipe-bom/2.0.0 |
We're glad to have you verify our work early; to reply quickly to the above: the new class is at: |
I had a Still not sure how to add the dependency. I have no success with - rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:1.19.4"))
+ rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:2.0.0"))
+ compileOnly 'org.openrewrite.recipe:rewrite-static-analysis:1.0.0' and no success with - rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:1.19.4"))
+ rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:2.0.0"))
+ rewrite(platform("org.openrewrite.recipe:rewrite-static-analysis:1.0.0")) |
I've had a quick look; right now you're using: rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:1.19.3"))
rewrite("org.openrewrite.recipe:rewrite-logging-frameworks") I'd expect things to work when using:
Given that rewrite-recipe-bom-2.0.0.pom manages the version of rewrite-static-analysis-1.0.0.pom Does that work on your end? |
Thank you for the patience and quick look. I indeed did it locally only - and did not push anything. Included your changes and comments (JabRef/jabref@7f6f080) and removed recipies no longer being available (JabRef/jabref@618996c) Is there a chance that I think, I won't miss MethodParamPad, PadEmptyForLoopComponents, UnnecessaryParentheses that much. UnnecessaryParentheses caused internal discussions (JabRef/jabref#9876 (comment)) ^^. |
Good to see those updates already; the SimplifyBooleanExpression never moved; that's still available by default in the original package. |
One more additional dependency for me then? ^^ - Shouldn't it move, too? |
You don't need a dependency for the recipes (still) in the original cleanup package. We've kept the recipes that we call directly from other recipes in openrewrite/rewrite. The others we have since moved to rewrite-static-analysis, as you've found. We're still in the midst of this release and documenting it all, so I appreciate you trying it out and finding where we should provide guidance in the migration. |
I summarize what we discussed, maybe it helps: Migration guide
|
@mike-solomon see the above comment for when it comes time to document and announce the new release. we might even be able to automate some of those moved recipe changes in code and yaml files. Also captured in openrewrite/rewrite#3234 |
I think, this thing is really in flux, therefore, I just comment here instead of rasing a new issue. Bumping org.openrewrite.rewrite from 6.1.4 to 6.1.6 (JabRef/jabref#10037) leads to following error:
I was hoping that an increase of a patch version does not lead to errors during usage. The solution is unfortunately not to bump org.openrewrite.recipe:rewrite-recipe-bom from 2.0.1 to 2.0.2 at the same time (tried at JabRef/jabref#10040). Of only that is bumped, it fails too. |
There has unfortunately been a bit of a botched change recently, which was subsequently reverted, that changed the signature of the MethodMatcher. It should all work again with the latest versions, so it's curious to hear you're having these issues. In general we recommend using all the latest version, but if there's a combination that's not working yet we should maybe bring out an additional patch release to get things going. |
We're squashing every last instance of that We've also documented the changes needed to pick up OpenRewrite 8.x over on Would you agree with closing the issues as done @koppor ? Or is there anything you'd want to still tackle as part of this issue, or in a subsequent issue? |
For me, the upgrade worked with your help. Thank you again. - The linked update doc looks good. In case, I miss something at subsequent updates, I'll raise my voice. |
Think, I need to drop recipies at the update. - id 'org.openrewrite.rewrite' version '6.1.4'
+ id 'org.openrewrite.rewrite' version '6.1.7'
- rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:2.0.1"))
+ rewrite(platform("org.openrewrite.recipe:rewrite-recipe-bom:2.0.2")) Would be nice if the default error output would include the failed recipe, because manually disabling recipeies one by one is difficult. And there is no good "gid bisect" equivalent for the
|
The |
When updating from 5.40.6 to 6.0.0, I get following output:
I checked https://docs.openrewrite.org/running-recipes/getting-started, but that still lists 5.40.6.
I checked the diff v5.40.5...v6.0.0, but could not see why this happens.
Full project setup at https://github.com/JabRef/jabref/blob/76c35f0afb6f9c700ee35a5475bbe9ff612fa75c/build.gradle#L487
The text was updated successfully, but these errors were encountered: