This message was deleted.
# community-support
s
This message was deleted.
r
Another thing to mention: I've also tried only adding the fixtures.jar however the helper class has a dependency on flyway, therefore when using it in my other project I receive a class Not Found error. That's why I'm trying to pack the whole module (so that I have access to sql files and dependencies).
e
you shouldn't be using the jar directly
if you simply publish to maven, gradle will publish the test fixtures as its own artifact by default, along with metadata about dependencies (as usual)
r
hey ! I've just tried to publish it to my local maven repo and it worked. however, there's still the issue of my flyway migrations. now it does indeed see the flyway dependency but it cannot see the location of the migrations in the filesystem. any suggestions ? edit: thanks for taking the time to answer !
so basically, is there anyway to also ship the folder with the sql migrations so that the helper class can still see them ?
e
extra files are usually distributed as resources (eg
src/main/resources/*
) but I don't know details about flyway
r
while my question certainly drifts a bit off topic, I still think it's in test-fixtures scope. let me rephrase: if I'm hardcoding a file path in src/testFixtures that points to resources (outside src/testFixtures but gets packaged in the jar) will classes from testFixtures have access to that ? really sorry in advance if my understanding is not correct
e
no, not by file path. you can access it by resource name though
1
r
thanks for all the answers. I did manage to pass the file path by including "classpath:" in front of the string