-
Notifications
You must be signed in to change notification settings - Fork 159
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
[EXPERIMENT] Try out MIMA 3.0.0-alpha-2 #1716
base: main
Are you sure you want to change the base?
Conversation
This PR is **not for merge**. It's sole purpose is to get more funny GIFs. Note: resolver alpha-3 has since known bugs and most of them are fixed, but this release is still ok to fiddle against Central.
Maven 4.0.0-alpha-9 is out, and Resolver 2.0.0-alpha-4 is on vote (with several HTTP/2 transport bugfixes). Once that is out, will do a MIMA 3.0.0-alpha-2 release where the "order is restored" (apache on java8, jdk HTTP/2 transport on java11+), hence JBang should work as usual from Java 8 and on, but on 11+ it will dynamically switch to HTTP/2 jdk transport. |
... or jetty transport if you want few floppies more, as it is best transport, with downside of relatively huge dep trail, while jdk transport is dep-less (while ASF httpClient is still there but unused on Java11+) |
Has many of issues from alpha-1 fixed, apache is present and works on Java8 as well, but some UTs still fail.
Updated to alpha-2 and fixed some bits (and removed Detector maven-plugin for now, as it pulled in whole Maven internals 3.x that clashes with mvn4)... |
JBang produces this error: https://issues.apache.org/jira/browse/MRESOLVER-464 |
All tests but one pass (MIMA alpha-2 has Resolver 2 alpha-6 that suffers from https://issues.apache.org/jira/browse/MRESOLVER-464 that is fixed on master). Locally verified fix works and JBang UT does not fail. There is one question in last commit. |
am i blind? dont see a question? |
@maxandersen here c1056d6#diff-64a760dbb76590786d34adfa898d9afebcbf8a16f6cb43e388bc4fdd50e9983eR128 |
This PR is not for merge. It's sole purpose is to get more funny GIFs with floppies.
Note: maven and resolver alphas since their release has known bugs and issues. While most of them are fixed, these are the latest alphas available from Central. But, this release is still ok to fiddle against Central (but may not support some special cases like proxies, whatnot). If you build JBang from this PR, it will use the latest "jdk" HTTP/2 transport (while old "apache" transport is dropped).
MIMA 3.0.0-alpha-2 release:
https://github.com/maveniverse/mima/releases/tag/release-3.0.0-alpha-2
Note: to build this locally you probably need
-x test
as alpha release may (and probably) has problems like proxy etc support. Still, the resulting distro should be fine to "test drive" in trivial situations like against Central and see HTTP/2 in action.