Skip to content
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

Repro dokka NoClassDefFoundError #5

Closed
wants to merge 2 commits into from

Conversation

dagguh
Copy link
Contributor

@dagguh dagguh commented Jun 12, 2024

See 806c334 message.
I can't merge this because:

So this test can repro, but cannot be used to confirm fixes.

  • DON'T MERGE

@dagguh dagguh requested a review from a team as a code owner June 12, 2024 16:23
dagguh added 2 commits June 12, 2024 18:24
After bumping to gradle-release:0.8.0, docker-infrastructure [fails publishing].
The `PublishTest` cannot reproduce it with `withPluginClasspath`, it hides the problem.
But then, the test project has to specify `gradle-release` version (0.9.0 here),
or otherwise it cannot resolve the unnamed version we're currently testing/building.

So this test can repro, but cannot be used to confirm fixes.

When minimizing the repro in `Fixtures`, I accidentally discovered
that the order of Gradle plugins matters. The problem goes away when `gradle-release` goes first.
The buildscript/plugin classpath is a fascinating mess.

[fails publishing]: https://github.com/atlassian/docker-infrastructure/actions/runs/9481104563/job/26126902514
This part wasn't necessary to repro a red ReleaseTest
back when it was introdiced in 3394c75
@dagguh dagguh force-pushed the repro-dokka-NoClassDefFoundError branch from 6cc9d41 to 80639b7 Compare June 12, 2024 16:24
@dagguh dagguh closed this Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant