Open trevan opened 2 years ago
This is most likely caused by the testFixturesAnnotationProcessor
configuration not having any kind of relationship with the main annotationProcessor
configuration.
I am actually surprised that it works between annotationProcessor
and testAnnotationProcessor
.
The easy fix is to add the platform to the testFixturesAnnotationProcessor
configuration as you've done for others.
I'll keep digging to figure out why it works between main
and test
.
@ljacomet , if there have been any recent updates or changes related to adding the platform to the testFixturesAnnotationProcessor.
The
testFixturesAnnotationProcessor
is not resolving the version that is defined as a constraint in a platform.In the attached zip file, there are two modules: platform and lib.
Platform's build.gradle is:
Lib's build.gradle is:
If you run
build
withwithoutVersion
set to false, then the build succeeds. The dependencies defined intestFixturesApi
andtestFixturesImplementation
all resolve correctly from the platform andtestFixturesAnnotationProcessor
resolves because there is a version specified. But if you changewithoutVersion
to true, then the build will fail. It complains about unable to resolveorg.projectlombok:lombok
.Expected Behavior
The platform constraints should be used by
testFixturesAnnotationProcessor
just likeapi
,implementation
,annotationProcessor
,testImplementation
,testAnnotationProcessor
,testFixturesApi
, andtestFixturesImplementation
.Current Behavior
testFixturesAnnotationProcessor
is not utilizing the platform constraints and requires a version to be specified.Context
Steps to Reproduce
annotationProcessorBug.zip
Your Environment
Build scan URL: