Fixed
Status Update
Comments
sp...@google.com <sp...@google.com> #2
Should we transform it from
fun <FileTypeT: FileSystemLocation> add(
type: MultipleArtifact<FileTypeT>,
artifact: FileTypeT
)
to
fun <FileTypeT: FileSystemLocation, Appendable> add(
type: MultipleArtifact<FileTypeT>,
artifactProvider: Provider<FileTypeT>
)
should we also share with Artifacts interface: ArtifactsImpl.appendTo ArtifactsImpl.appendAll. They are not in use right now. Maybe part of another ticket?
sp...@google.com <sp...@google.com> #3
I don't think we can just move it to use a Provider<> as the original bug called for adding a file.
plus this add() would become just like to OperationRequest::toAppendTo no ?
bl...@google.com <bl...@google.com>
bl...@google.com <bl...@google.com>
an...@google.com <an...@google.com> #4
So we somehow need to disallow calling this method if FileSystemLocation is produced by task?
Can we add some validation on build phase - meaning we can call those only during config but not when tasks execute?
plus this add() would become just like to OperationRequest::toAppendTo no ?
it looks like it
Description
Currently, if a user runs
gradlew updateLintBaseline
and there is aLintError
issue (i.e.,"Unexpected failure during lint analysis (this is a bug in lint or one of the libraries it depends on)..."
), theLintError
issue gets added to the lint baseline xml.In cases like this, the build should fail, and the lint baseline should not be modified.