http://forums.gradle.org/gradle/topics/signing_plugin_add_to_configuration_even_if_its_not_being_run
The signing plugin adds PublishArtifacts for each signature file. These
signature files may not actually be created depending on the signing
configuration:
signing {
required { project.taskGraph.hasTask("uploadArchives") }
sign configurations.archives
}
This “required” handling makes it easy to have a build that works for people
who don't have their environment set up for signing. If signing is not
required, and we can't sign, the signing task(s) is skipped so we end up with
the PublishArtifacts on the configuration pointing to non existent files.
The problem comes in that the Artifactory plugin tries to upload these non
existent files and explodes.
One idea is to allow this as part of the model. That is, a PublishArtifact
becomes something that might be created during the build instead of something
that will be created.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
