tree cbe408df590878a1478907b8106482ec11f93cfd
parent 3fdd3fe70489f7ee8bca9b690eff5f074a939ce1
author dkhalanskyjb <52952525+dkhalanskyjb@users.noreply.github.com> 1585320080 +0300
committer GitHub <noreply@github.com> 1585320080 +0300
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJefhCQCRBK7hj4Ov3rIwAAdHIIAGspBJJqtfAYceuznt6WmLEq
 fv3WRugCQXqUZpd3Hw6YWHOEjy+R7OPLohF23qlaIvk+bJo6BEKL+xKvQV0FHip9
 jzdP7l9fMbrryVmpyL510QJ0M4vOFyv/YiMNsodEC9nXlRfH6Eb8Ian8IsjlO9qw
 iPH3BTTyXcmgsDS+ZNq6Af94CGHzIes5/3XT5wud1taak0+iqI3W822XQrZ323CB
 1cnfKcplpyqXwxzp+iXyJDdtSKofq5N/wozySmr1xbegnUPlXiDO+XXSkuBJ7eh5
 45LCyKC30TfnLvn9V9GSQVQk9gvC9qyWr544Ay/1p7j1oWT9APlvAxlyPJqOc0g=
 =fo0i
 -----END PGP SIGNATURE-----
 

Fix publication validator not looking in the local maven repository (#1880)

During the change of the publication validator, a bug was
introduced that led to MavenPublicationValidator being run not on
the artifacts from the local Maven repository but on classfiles
from the corresponding subproject. This is a problem because this
test is for the behavior of the atomicfu plugin, which could in
theory produce nice classfiles in one place but wrong ones in the
other, and the only important thing to test is whether the
published classfiles are good.

Now, this is fixed.