-
Notifications
You must be signed in to change notification settings - Fork 8
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
Migrate to ApacheHttpClient 5.x recipe updates org.apache.httpcomponents.core5: httpcore5 to version 5.3.x #28
Comments
Hi @smoring2 ; That's quite odd! Let me first link the relevant parts of the recipe and recipe tests. rewrite-apache/src/main/resources/META-INF/rewrite/apache-httpclient-5.yml Lines 38 to 43 in 75ca72c
rewrite-apache/src/test/java/org/openrewrite/apache/httpclient5/UpgradeApacheHttpClient5Test.java Lines 47 to 85 in 78d8e8a
As you can see the recipe uses our XRange version selector. The unit test then verifies that the last This might be something to do with how those version ranges are resolved against the unexpected versioning pattern for httpcore5 in openrewrite/rewrite. |
What version of OpenRewrite are you using?
I am using
How are you running OpenRewrite?
mvn -U org.openrewrite.maven:rewrite-maven-plugin:5.35.0:run -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-apache:1.4.2 -Drewrite.activeRecipes=org.openrewrite.apache.httpclient5.UpgradeApacheHttpClient_5 -Drewrite.exportDatatables=true
I am using the Maven plugin, and my project is a single module project.
What is the smallest, simplest way to reproduce the problem?
What did you expect to see?
What did you see instead?
5.3.x could not be resolved from maven central https://mvnrepository.com/artifact/org.apache.httpcomponents.core5/httpcore5
What is the full stack trace of any errors you encountered?
Are you interested in contributing a fix to OpenRewrite?
The text was updated successfully, but these errors were encountered: