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

Do not require a compileOnly configuration to be present #67

Merged
merged 1 commit into from
Jan 3, 2025

Conversation

timtebeek
Copy link
Contributor

As reported via Slack:

* Where:
Build file '/Users/greg/git/rewrite/rewrite-bom/build.gradle.kts' line: 1

* What went wrong:
An exception occurred applying plugin request [id: 'org.openrewrite.build.publish']
> Failed to apply plugin 'org.openrewrite.build.publish'.
   > Configuration with name 'compileOnly' not found.

@timtebeek timtebeek added the bug Something isn't working label Jan 3, 2025
@timtebeek timtebeek self-assigned this Jan 3, 2025
Copy link

@greg-at-moderne greg-at-moderne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't tested it, but the defensive null-checks make sense.

The docs for findByName indeed indicate null response if not found:
https://docs.gradle.org/current/kotlin-dsl/gradle/org.gradle.api/-named-domain-object-collection/find-by-name.html

@timtebeek timtebeek merged commit 1581112 into main Jan 3, 2025
1 check passed
@timtebeek timtebeek deleted the do-not-require-compileOnly branch January 3, 2025 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants