timtebeek commented on PR #1557: URL: https://github.com/apache/wicket/pull/1557#issuecomment-6057081928
Thanks for the tag @martin-g and sorry to hear about your troubles. It's indeed an access permission issue. The CGP offers free downloads for any Apache licensed modules, but the three you've referenced fall under Moderne Source Available License: https://docs.moderne.io/user-documentation/recipes/accessing-the-code-genome-project/#what-the-repository-hosts Those modules are still source available for folks to build and run within the terms of the license, but we don't offer binaries for those to non-customers, which is tripping you up here. Looking across which recipes are used & pulled in here they seem to come in through these two https://github.com/apache/wicket/blob/003cf99a60c641c9225665e008b368d2de9aa29f/wicket-migration/src/main/resources/META-INF/rewrite/wicket.yml#L17-L18 That brings us to a few different ways forward: 1. Pin to an older version of either the bom, or the specific recipe modules; not ideal, but the quickest way forward for now. Note that you'll want to use `rewrite-recipe-bom:3.37.0` for the latest version on Maven Central for the recipe modules. The 3.38.0 release should not have gone to Central. 2. Take out the MSAL licensed recipes and modules here; users can still procure and run those MSAL recipes themselves, making this purely handle the Wicket side of the migration. Others like Quarkus have opted for this approach as well, depending only on our Apache licensed modules. I understand neither is ideal from a user perspective, but it's what I can offer based on decisions beyond my control. -- 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]
