-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Update dokka-maven-plugin and put it into build-parent #17355
Conversation
A much more convoluted PR is already there: #16842 |
@gsmet our job to deploy Quarkus main artifacts to internal Artifactory doesn't work now because of usage of dokka 1.4.30 maven plugin which depends on kotlinx-html-jvm 0.7.2 which is not available. If #16842 doesn't get merged within few days I would prefer reopening this PR and merging it so we can deploy Quarkus daily builds and run the community related tests in the lab. |
@evanchooly sorry, it will conflict with your work but we can't just wait anymore as we can't do a full release build anymore. |
Then why not merge that other one? |
Checked with the release process, let's merge. Thanks @rsvoboda ! |
@evanchooly was it ready? I kinda lost my hope on this given the information you gave me. |
🚫 This workflow run has been cancelled. Failing Jobs - Building e84b766
|
Update dokka-maven-plugin from 1.4.30 to 1.4.32 and put it into build-parent.
dokka-maven-plugin was use 3 times, twice in
deploy
phase, once inpackage
phase.Now synced to
deploy
phase, @gsmet fyi as you did 98f655aUpdate to 1.4.32 version is needed as 1.4.30 depends on kotlinx-html-jvm 0.7.2 which is not available
https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-html-jvm/ ... only 0.7.3 is available