https://gradle.com/ logo
Join Slack
Powered by
ok, this doesn't make any sense to me. in project ...
# community-support
c
ok, this doesn't make any sense to me. in project 
model
it has 
transaction-api
on 
testRuntimeClasspath
but it does not have the appropriate 
cdi
dependency. The only difference I can see from this and the 
jpa
project is that that gets the dependency through an implementation where 
spring-data-jpa
is included directly. Whereas model gets it from a 
testRuntimeOnly
that uses 
starter-jpa
The component metadata rule should be being applied to that too, no? https://github.com/xenoterracide/spring-app-commons/pull/95/files#diff-5625e3601fa0ad3a6a2824239e5a2fde71c149597d31394f9224a08c24be7b9dR57-R70 https://scans.gradle.com/s/5acc7lwxebsp6/dependencies?dependencies=transaction&expandAll&toggled=W1syLDBdLFsyLDBdXQ
@Vampire since this was your idea... why am I not getting the dependencies in all the places?
v
I neither see the cdi dependency for jpa, nor for model as dependency of transaction-api in your build scan :-/
In jpa it is just there because you have an explicit dependency
c
oh, must've missed that so why aren't they there implicitly because of the component metadata
right now the component metadata rules don't do anything, although I think I fully applied in my settings as suggested
v
I have no idea, maybe some bug? 🤷‍♂️
🤣 1
c
well... I assumed I had applied the rules incorrectly
I'm gonna remove the rules assuming component metadata is fundamentally broken
v
They always worked fine for me
If there is a bug, you probably hit some edge case
c
shrugs
well I assume if it looks like I did it correctly to you, then it's a bug and fundamental breakage to me
seems I always hit so called edge cases
v
Quite possible
c
but I never feel like I'm doing anything weird
v
We seldomly feel we are doing something weird, even if we do 😄
c
feel free to tell me what's weird 😉
v
Nope, not going to analyze your whole build to find the potential weirdness that might trigger this edge case
c
I just meant in genal 😉
general*
3 Views
Open in Slack
PreviousNext
Powered by