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

Avoid Gradle internal API CompositeProjectComponentArtifactMetadata #29622

Conversation

aloubyansky
Copy link
Member

No description provided.

@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle labels Dec 1, 2022
Copy link
Member

@glefloch glefloch left a comment

Choose a reason for hiding this comment

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

Nice catch. We definitely need to avoid calling gradle's internal api

@gsmet
Copy link
Member

gsmet commented Dec 2, 2022

@aloubyansky I have a lot of conflicts when backporting this one to 2.14. I'm wondering if we actually need to backport it. Could you check?

@aloubyansky
Copy link
Member Author

@gsmet feel free to skip it then. We can revisit in case someone complains.

@@ -28,7 +28,6 @@
import org.gradle.api.tasks.SourceSet;
import org.gradle.api.tasks.SourceSetContainer;
import org.gradle.api.tasks.compile.AbstractCompile;
import org.gradle.composite.internal.CompositeProjectComponentArtifactMetadata;
import org.gradle.internal.composite.IncludedBuildInternal;
Copy link
Member

Choose a reason for hiding this comment

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

@aloubyansky @glefloch isn't this class internal too? Wondering if there are alternatives.

Copy link
Member Author

Choose a reason for hiding this comment

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

It is. It's not obvious how to avoid it for me. Ideally, we don't want to rely on internal API. @glefloch if you have some time to research this one, it'd be very much appreciated.

Copy link
Member

Choose a reason for hiding this comment

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

yes I will have a look on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants