openrewrite / openrewrite/rewrite-migrate-java
Possible regression in 6.37.0 version
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 156
- Forks
- 130
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 21
Description
What version of OpenRewrite are you using?
I am using
- org.openrewrite:rewrite-maven-plugin 6.37.0
- Maven 3.6.3
How are you running OpenRewrite?
Maven Command Line
What is the smallest, simplest way to reproduce the problem?
I copied the jakarta 10 migration example in a personal project
mvn -U org.openrewrite.maven:rewrite-maven-plugin:run --define rewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-migrate-java:RELEASE --define rewrite.activeRecipes=org.openrewrite.java.migrate.jakarta.JakartaEE10 --define rewrite.exportDatatables=true
What did you expect to see?
Jakarta10 rules applied in the project within seconds.
What did you see instead?
Using new version 6.37.0, it took 5minutes to complete the process. However, using version org.openrewrite:rewrite-maven-plugin v6.36.0, the process completed in seconds in the same project.
What is the full stack trace of any errors you encountered?
It didn't throw an error. But the SourcesFileResults.csv file in v6.37 has 2500+ rows. In contrast, v6.36 file only generates 8 rows
Are you interested in contributing a fix to OpenRewrite?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the supplied Maven command with rewrite-maven-plugin 6.36.0 and 6.37.0 against the same Jakarta EE 10 migration project, then compare execution time and SourcesFileResults.csv. Trace the JakartaEE10 recipe execution to identify why 6.37.0 produces 2,500+ rows instead of 8; done means the regression is reproduced, explained, and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100