Luke Daley-2 wrote: > > only the artifacts that exist as part of this configuration at the time > you specify you want to sign it will be signed. >
Are you saying that the artifacts to be signed must have been added to the configuration before the signing plugin gets configured? If so, why is this necessary, and is there a way to avoid it? As far as I know, most tasks that have configurations as their inputs only access them at execution time, avoiding this problem. I guess one reason why Configurations don't have these listeners is that they aren't DomainObjectCollections. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Artifact-added-to-configuration-listener-tp4541993p4543491.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
