Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: Put MIMA in action (#1604)
* Put MIMA in action Re-use MIMA in ArtifactResolver, and properly handle repoSys shutdown. * Fix shading * A bit bigger commit 8 tests are failing, will figure out later. * Use released, fix tests * Revert "A bit bigger commit" This reverts commit 903b9a9. * refactor: created alternative way for getting local maven repo path * Update and use static-uber runtime As sisu is not good candidate for minification... * Use 1.1.2 MIMA As older did not honor maven.repo.local in same way as Maven would. * Remove as it is unneeded The static-uber behaves under minimization, unlike sisu as there are code refs. * LoggingEnabled was still false No need for private member, just setup logging if needed, otherwise dont * Disable shaded jar minimization As it is plain broken it seems. No way to NOT remove org.slf4j.spi package (the one we KNOW about) but who knows what else it removes down the road. * Simplify * Use MIMA 2.0.0 * Add --verbose to 1st invocation * Use MIMA 2.1.0 That has several crypto related bugs fixed: https://github.com/maveniverse/mima/releases/tag/release-2.1.0 * fix: explicit exclude standalone static from minimization * Update MIMA, add required dep (httpClient) * By default non-HTTPS reposes are disabled so assertions failed. * One more http->https * Move off from deprecated methods * Align minimize config w/ changes * Up to Mima 2.3.5 That is Maven 3.9.5 + Resolver 1.9.16 Remove embedded-maven (JBang will not run within Maven embedded) and remove unneeded append command as sisu index is already merged in static. * Upgrade to MIMA 2.4.0 * Upgrade MIMA to 2.4.2 * Use default it no repo given The semantics of .repositories() changed, as it was not possible to configure MIMA without remote repositories but sometimes you need that. Before, it always prepended Central. Also, there is new "op" what to do with provided list, when repositories discovered from settings.xml are considered as well. * Simplify and better express intenty * Ignore settings.xml discovered repositories, JBang drives this * Update ot MIMA 2.4.3 It picks up latest Resolver 1.9.18 that causes less surprises to Windows users. --------- Co-authored-by: Tako Schotanus <[email protected]> Co-authored-by: Max Rydahl Andersen <[email protected]>
- Loading branch information