dashorst opened a new issue, #1755:
URL: https://github.com/apache/wicket/issues/1755
Master's copy of `org.apache.wicket.MigrateToWicket10` in `wicket-migration`
has the same defect as the 10.x line (#1752): a Wicket 9 project that depends
on `org.apache.wicket.experimental.wicket9:wicket-metrics` keeps that
dependency at its Wicket 9 groupId and 0.x version after migration.
The recipe tries to migrate the experimental modules with two identical
steps:
```yaml
- org.openrewrite.maven.UpgradeDependencyVersion:
groupId: org.apache.wicket.experimental.wicket9
artifactId: "*"
newVersion: 10.x
```
The `experimental.wicket9` artifacts were only published with 0.x versions,
so the `10.x` range finds nothing. In Wicket 10, `wicket-metrics` is published
under `org.apache.wicket.experimental.wicket10`.
On `wicket-10.x` this was fixed by #1753 (91e28d883e), which replaces both
steps with a `ChangeDependencyGroupIdAndArtifactId` from
`experimental.wicket9:wicket-metrics` to `experimental.wicket10` at `10.x`. The
same change applies to master unchanged.
Affected: `wicket-migration` on master, including the 11.0.0 release
candidate. On master the recipe is reached through `MigrateToWicket10` and
`BestPractices`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
