This message was deleted.
# community-support
s
This message was deleted.
v
Are you sure that's a good idea? NONE is really very rarely helpful. May I ask why you think relative is still too strict?
c
Sure thing 🙂 The Plugin adds a Code Quality Check. And the tool it uses accepts a config xml file via command line arg. IMO, the result of the task is determined by the content of this config file and not its location. Also,
PathSensitivity.NONE
really does not play well with
TextResource
v
I guess you mean RELATIVE does not play well with text resources? 🙂
c
Yes, thats what I meant 😄
v
Well, for the latter part you could have a task that copies the textresource to some location that always has the proper same relative path, like copying to
temporaryDir
of the task, or copying to
layout.buildDirectory
. Changing those annotations of an existing task is not trivial afair. I'm not 100% sure, you might try to subclass the task and override the property in question. If that does not work, you might only have the choice to monkey-patch the task class by copying it to your
buildSrc
and fixing what you need to, adding some mechanism to make sure you remember to update that file when you change the plugin version.
buildSrc
classes are in a class loader above the project classpath class loaders so classes in it will be preferredely used.
c
Alright 🙂 Thanks for the info 🙂 Guess I'll go with the first solution
👌 1