On 18 July 2012 10:51, Luke Daley <[email protected]> wrote: > > On 21/06/2012, at 1:06 AM, Adam Murdoch wrote: > > The plan is the same as last time we discussed it: > 1. Model publications as things, independent of destination. > 2. Model signature generation as a transformation of a thing. > 3. Model conditional configuration using build types. > 4. Add a plugin that wires the above together in an opinionated way (e.g. > all publications of type x must be signed). > > We really only need 3) to solve the use case, though. > > > What's the final result here? How are we proceeding? >
In order to deprecate the old behaviour (ignoring missing artifacts), and not emit warnings for signing artifacts, I just hacked in a check: we ignore missing 'signing' artifacts, but emit a deprecation warning for anything else. We're only checking for the built-in signing artifact extensions, which is pretty lame, but allows us to proceed until we have a better solution. Daz
