Currently, the ConstraintFile implementation uses Files.lines to read in values from the dependency properties file. It turns out that the stream returned from this function is a rare occurrence where a Stream's close method must be invoked
Without close behavior implemented, this is currently a resource leak, and can cause issues modifying the file after accessing it via the plugin (running a build where this file has been modified, then trying to check out another Git branch will fail, at least in some OSes, for example)
Currently, the
ConstraintFile
implementation usesFiles.lines
to read in values from the dependency properties file. It turns out that the stream returned from this function is a rare occurrence where a Stream's close method must be invokedWithout close behavior implemented, this is currently a resource leak, and can cause issues modifying the file after accessing it via the plugin (running a build where this file has been modified, then trying to check out another Git branch will fail, at least in some OSes, for example)