On 02/07/2011, at 8:44 AM, Peter Niederwieser 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?
Not that I can see, without tracking new things added to the configuration. The signing plugin has to create one-to-one publish artifacts for the publish artfacts that are part of the configuration. One option would be to delay creating the signature publish artifacts until the last minute but this closes the door on all kinds of fine tuning and is generally contrary to the Gradle approach. The best solution would be to just add/remove signature artifacts as the source configuration is modified. > As far as I know, most tasks that have configurations as their inputs only > access them at execution time, avoiding this problem. Yeah, but that doesn't really apply here because the signing plugin needs to populate the model during configuration time based on the source configuration. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
